Merge pull request #807 from vtexdocs/fix/hyphenation

Fix/hyphenation

docs/guides/Getting-Started/getting-started/getting-started-platform-overview.md

@@ -40,16 +40,16 @@ As a true multi-tenant cloud platform, all our clients take advantage of the sam
 
 ## VTEX IO
 
-[VTEX IO](https://vtex.io) is our enterprise low-code development platform that helps you deliver commerce solutions faster. From smooth, PWA-ready stores, to custom admin interfaces and back-end integrations, it offers an opinionated set of frameworks that allow you to evolve fast and safely.
+[VTEX IO](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-io) is our enterprise low-code development platform that helps you deliver commerce solutions faster. From smooth, PWA-ready stores, to custom admin interfaces and backend integrations, it offers an opinionated set of frameworks that allow you to evolve fast and safely.
 
 **Transformation should be powered by technology, not limited by it.** Work with highly productive technologies like TypeScript, React, GraphQL, .NET and Node, using simple and intuitive frameworks which you can learn on-the-go. Become productive in record time with just a command line code application and stop running your code locally — deploy and publish all changes to our cloud development environment seamlessly.
 
 With VTEX IO, you can build:
 
-- Comprehensive shopping experiences that never get old
-- Custom storefront apps
-- Custom admin apps
-- Custom back-end integrations.
+- Comprehensive shopping experiences that never get old.
+- Custom storefront apps.
+- Custom admin apps.
+- Custom backend integrations.
 
 Check out our [App Store](https://apps.vtex.com) and documentation.
 

docs/guides/Getting-Started/search-overview.md

@@ -70,7 +70,7 @@ You can provide your customers with a more customized experience navigating the
 
 ## Integrating an external search provider with VTEX
 
-The [Search Protocol](https://developers.vtex.com/vtex-rest-api/docs/search-integration-guide) defines the contract between an external search provider and a VTEX store running on VTEX IO. If a search provider adheres to this protocol, it can completely replace the original VTEX search capabilities without needing to implement any front-end pages or react components.
+The [Search Protocol](https://developers.vtex.com/vtex-rest-api/docs/search-integration-guide) defines the contract between an external search provider and a VTEX store running on VTEX IO. If a search provider adheres to this protocol, it can completely replace the original VTEX search capabilities without needing to implement any frontend pages or react components.
 
 - [Overview](https://developers.vtex.com/vtex-rest-api/docs/external-search-provider-overview)
 - [Specification](https://developers.vtex.com/vtex-rest-api/docs/external-search-provider-specification)

docs/guides/Integration-Guides/catalog-integration/specifications.md

@@ -59,7 +59,7 @@ For example, in a fashion store you would be able to create a product specificat
 
 This information could be displayed as a filter in the search navigation menu or as an informative text inside the product page.
 
-Product specifications can receive data such as strings and numbers, which VTEX APIs then consume and use for front-end customizations or to send information to external integrations.
+Product specifications can receive data such as strings and numbers, which VTEX APIs then consume and use for frontend customizations or to send information to external integrations.
 
 ### SKU Specifications
 

docs/guides/Integration-Guides/payments-integration-guide/how-the-integration-protocol-between-vtex-and-antifraud-companies-works.md

@@ -39,7 +39,7 @@ If the partner is a SI (Service Implementer) developing integrations for clients
 
 ### 1. Implementing the protocol
 
-Before setting up the VTEX environment, the provider must implement the back-end service required to process the anti-fraud services (API). For more information, access the [Anti-fraud Provider Protocol API](https://developers.vtex.com/docs/api-reference/antifraud-provider-protocol).
+Before setting up the VTEX environment, the provider must implement the backend service required to process the anti-fraud services (API). For more information, access the [Anti-fraud Provider Protocol API](https://developers.vtex.com/docs/api-reference/antifraud-provider-protocol).
 
 > ⚠️ You can also access our [template on GitHub](https://github.com/vtex-apps/antifraud-provider-example) to help you quickly develop your anti-fraud connector using the Anti-fraud Provider Protocol and VTEX IO.
 

docs/guides/Integration-Guides/payments-integration-guide/payments-integration-implementing-a-payment-provider.md

@@ -288,7 +288,7 @@ Refer to the [Post Refund Payment](https://developers.vtex.com/docs/api-referenc
 
 The Inbound Request (BETA) implements an URL that facilitates a direct connection between our Gateway service and the Payment Provider.
 
-It is responsible for the communication with the provider's back-end through our gateway, relying on the security of sending the context of the transaction by VTEX.
+It is responsible for the communication with the provider's backend through our gateway, relying on the security of sending the context of the transaction by VTEX.
 
 An example of the request is:
 

docs/guides/Integration-Guides/search-integration-guide.md

@@ -5,7 +5,7 @@ hidden: false
 createdAt: "2020-09-11T16:42:03.604Z"
 updatedAt: "2022-04-28T18:33:13.280Z"
 ---
-The Search Protocol defines the contract between an external search provider and a VTEX store running on VTEX IO. If a search provider adheres to this protocol, it can replace completely the original VTEX search capabilities without needing to implement any front-end pages or react components.
+The Search Protocol defines the contract between an external search provider and a VTEX store running on VTEX IO. If a search provider adheres to this protocol, it can replace completely the original VTEX search capabilities without needing to implement any frontend pages or react components.
 
 The main idea is to provide the ability for a search provider to integrate with the minimum amount of work necessary and a VTEX customer to easily switch search providers without having to change anything in the storefront.
 [block:html]

docs/guides/Integration-Guides/search-integration-guide/external-search-provider-overview.md

@@ -8,9 +8,9 @@ updatedAt: "2020-10-30T20:44:33.600Z"
 
 A search engine is a crucial part of e-commerce. It can drive more sales if the search results are good and it can worsen the user experience if they are bad.
 
-Changing the search provider usually involved changing code both in the front-end and in the back-end, creating unnecessary friction.
+Changing the search provider usually involved changing code both in the frontend and in the backend, creating unnecessary friction.
 
-The idea behind the VTEX search protocol is to provide a clear contract between any VTEX store on VTEX IO and a search provider defined by a GraphQL schema. This contract enables low-effort switching between different search engines. And it also helps to speed up the development process of integration with a new search provider, because the integration will be completely decoupled from the front-end components.
+The idea behind the VTEX search protocol is to provide a clear contract between any VTEX store on VTEX IO and a search provider defined by a GraphQL schema. This contract enables low-effort switching between different search engines. And it also helps to speed up the development process of integration with a new search provider, because the integration will be completely decoupled from the frontend components.
 
 Search protocol benefits both developers and VTEX stores!
 

docs/guides/Integration-Guides/session-manager/adding-telesales-impersonated-email-using-the-session-manager.md

@@ -11,7 +11,7 @@ In order to allow this type of selling, VTEX offers the telesales feature, throu
 
 ## Telesales Toolbar 
 
-The [telesales toolbar](https://help.vtex.com/en/tutorial/telesales-toolbar--tutorials_5500) is the most straightforward way to use the telesales feature. A top bar appears on the store's front end once the registered operator logs in to the store environment. It is displayed in all site areas, except on the [My Orders screen](https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh#orders).
+The [telesales toolbar](https://help.vtex.com/en/tutorial/telesales-toolbar--tutorials_5500) is the most straightforward way to use the telesales feature. A top bar appears on the store's frontend once the registered operator logs in to the store environment. It is displayed in all site areas, except on the [My Orders screen](https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh#orders).
 
 These are the steps required to use the telesales toolbar:
 1. [Create a telesales user](https://help.vtex.com/tutorial/como-criar-um-usuario-de-televendas--frequentlyAskedQuestions_4227).

docs/guides/UI-Customization/my-account/ui-customization-my-authentication.md

@@ -7,12 +7,9 @@ updatedAt: "2021-07-07T17:35:14.452Z"
 ---
 
 This guide shows the steps to change the appearance of the Authentication tab in My Account using CSS.
-[block:callout]
-{
-  "type": "warning",
-  "body": "This guide is for stores that do not use VTEX IO, making the customization through CMS. If your store is a VTEX IO store, check the [My Authentication Customization Guide using IO](https://developers.vtex.com/docs/guides/vtex-io-my-authentication) article."
-}
-[/block]
+
+> ⚠️ This guide is for stores that do not use VTEX IO, making the customization through CMS. If your store is a VTEX IO store, check the [My Authentication Customization Guide using IO](https://developers.vtex.com/docs/guides/vtex-io-my-authentication) article.
+
 To customize the appearance of My Authentication components, first you have to create your own CSS file with the desired customization settings. Below you can find the list of CSS handles and a CSS file example.
 ![My Authentication CSS code Portal](https://cdn.jsdelivr.net/gh/vtexdocs/dev-portal-content@main/images/ui-customization-my-authentication-0.png)
 
@@ -75,14 +72,14 @@ Then go to the Admin of your store and do the following steps:
 2. Click on **CMS**.
 3. Click on **Layout**. You can also get here from the link `{accountName}.myvtex.com/admin/a/` replacing `{accountName}` for the name of your account.
    ![Admin menu Layout](https://cdn.jsdelivr.net/gh/vtexdocs/dev-portal-content@main/images/ui-customization-my-authentication-1.png)
-4. In the **Front-end CMS** left panel, navigate to **CMS** > **Files Manager** > **.css**.
+4. In the **Frontend CMS** left panel, navigate to **CMS** > **Files Manager** > **.css**.
 5. In the **Files Manager** tab, click on the **Add** button.
    ![CMS File Manager CSS](https://cdn.jsdelivr.net/gh/vtexdocs/dev-portal-content@main/images/ui-customization-my-authentication-2.png)
 6. In the **Files Maintenance** tab, click on the `Localizar` button.
 7. A window with a file explorer will open. Choose the CSS file you created.
 8. Click on the `Salvar arquivo` button. This will upload your CSS file to the CMS of the store.
    ![Add CSS file CMS](https://cdn.jsdelivr.net/gh/vtexdocs/dev-portal-content@main/images/ui-customization-my-authentication-3.png)
-9. In the **Front-end CMS** left panel, navigate to **CMS** > **HTML Templates** > **Account**.
+9. In the **Frontend CMS** left panel, navigate to **CMS** > **HTML Templates** > **Account**.
    ![CMS HTML Template Account](https://cdn.jsdelivr.net/gh/vtexdocs/dev-portal-content@main/images/ui-customization-my-authentication-4.png)
 10. In the right panel will appear the My Account HTML template. Inside the `<head>` section, insert the tag `<link href="https://{accountName}.vteximg.com.br/arquivos/{cssFile}" rel="stylesheet"></link>`, replacing `{accountName}` for the account name of your store and `{cssFile}` for the name of the CSS file you uploaded.
     ![My Authentication HTML code](https://cdn.jsdelivr.net/gh/vtexdocs/dev-portal-content@main/images/ui-customization-my-authentication-5.png)