From 0d43bd7ad02be63ebae02592590dc0f1dd4f5e8a Mon Sep 17 00:00:00 2001 From: sheilagomes Date: Fri, 23 Feb 2024 17:07:11 -0300 Subject: [PATCH] Fix broken links --- ...EXAdminstringstandardizationinEnglish.html | 8 +- ...EXAdminstringstandardizationinSpanish.html | 10 +- ...dminstringstandardizationinPortuguese.html | 4 +- .../VTEXLocalizationStyleGuideEN.html | 114 +++++++++--------- .../VTEXLocalizationStyleGuideES.html | 2 +- .../VTEXPortugueseStyleGuidePT.html | 42 +++---- .../VTEXWritingStyleGuideEN.html | 16 +-- .../WritingStyleGuideES.html | 26 ++-- .../VTEXWritingStyleGuidePT.html | 18 +-- 9 files changed, 120 insertions(+), 120 deletions(-) diff --git a/content/loc_admin_review_logs/Admin String Standardization - EN/VTEXAdminstringstandardizationinEnglish.html b/content/loc_admin_review_logs/Admin String Standardization - EN/VTEXAdminstringstandardizationinEnglish.html index 962bdd8..988267b 100644 --- a/content/loc_admin_review_logs/Admin String Standardization - EN/VTEXAdminstringstandardizationinEnglish.html +++ b/content/loc_admin_review_logs/Admin String Standardization - EN/VTEXAdminstringstandardizationinEnglish.html @@ -10,9 +10,9 @@

VTEX Admin string standardization for English

-

The VTEX Admin strings were fully reviewed as proposed in the 2022 third-quarter OKR of the Localization team. During this process, we applied grammar, tone, and voice corrections to offer a consistent experience for our users throughout platform strings. The review implemented patterns specified in our Localization style guides, the CAT tool integrated Localization glossary, VTEX UX Writing Guidelines, as well as naming and standardization discussions with PMs. In this document, we have included the main reference and standardization points that were applied during the review and that should be maintained in Admin strings.

+

The VTEX Admin strings were fully reviewed as proposed in the 2022 third-quarter OKR of the Localization team. During this process, we applied grammar, tone, and voice corrections to offer a consistent experience for our users throughout platform strings. The review implemented patterns specified in our Localization style guides, the CAT tool integrated Localization glossary, VTEX UX Writing Guidelines, as well as naming and standardization discussions with PMs. In this document, we have included the main reference and standardization points that were applied during the review and that should be maintained in Admin strings.

Capitalization

-

These patterns were adopted from the Voice Chart available in the UX Writing Guidelines.

+

These patterns were adopted from the Voice Chart available in the UX Writing Guidelines.

@@ -171,7 +171,7 @@

Capitalization

Grammar forms

    -
  • When naming menu items, remember that in EN, nouns acting as adjectives are used in the singular form. This especially applies to pages with “management” in their name: Offer Management, Affiliate Management, Order Management. Other examples are Custom Order Attributes, Order Authorization, and SKU Bindings.
  • +
  • When naming menu items, remember that in EN, nouns acting as adjectives are used in the singular form. This especially applies to pages with “management” in their name: Offer Management, Affiliate Management, Order Management. Other examples are Custom Order Attributes, Order Authorization, and SKU Bindings.

Lexical preferences

    @@ -186,7 +186,7 @@

    Lexical preferences

  • As a button taking you to another view, view is the preferred verb instead of “see”.
  • “Freight” and “shipping” were standardized to shipping.
  • The phrase “Do you really want to…” was updated to the more generally used Are you sure you want to…
  • -
  • The term “profile” was updated to “role” for user permissions as per the official change in terminology described in this announcement.
  • +
  • The term “profile” was updated to “role” for user permissions as per the official change in terminology described in this announcement.
  • The sentence placement of “here” was corrected. “Click here to” is a standard phrase, but in longer sentences, “here” is preferred at the end of the sentences: “Drop your file here” not “Drop here your file” or “Enter your message here” not “Enter here your message.”
  • “Search for” in the sense of “search using an attribute” to get a result set was corrected to Search by [ID, name, etc.]. If it is a placeholder, it can be shortened to simply search.
  • “Created at” was corrected to Created on. “On” is the right preposition to indicate a date (month and day or day). “At” is used to indicate time (hour).
  • diff --git a/content/loc_admin_review_logs/Admin String Standardization - ES/VTEXAdminstringstandardizationinSpanish.html b/content/loc_admin_review_logs/Admin String Standardization - ES/VTEXAdminstringstandardizationinSpanish.html index d734d85..b4cbcf7 100644 --- a/content/loc_admin_review_logs/Admin String Standardization - ES/VTEXAdminstringstandardizationinSpanish.html +++ b/content/loc_admin_review_logs/Admin String Standardization - ES/VTEXAdminstringstandardizationinSpanish.html @@ -10,7 +10,7 @@

    VTEX Admin string standardization for Spanish

    -

    The VTEX Admin strings were fully reviewed as proposed in the 2022 third-quarter OKR of the Localization team. During this process, we applied grammar, tone, and voice corrections to offer a consistent experience for our users throughout platform strings. The review implemented patterns specified in our Localization style guides, the CAT tool integrated Localization glossary, VTEX UX Writing Guidelines, as well as naming and standardization discussions with PMs. In this document, we have included the main reference and standardization points that were applied during the review and that should be maintained in Admin strings.

    +

    The VTEX Admin strings were fully reviewed as proposed in the 2022 third-quarter OKR of the Localization team. During this process, we applied grammar, tone, and voice corrections to offer a consistent experience for our users throughout platform strings. The review implemented patterns specified in our Localization style guides, the CAT tool integrated Localization glossary, VTEX UX Writing Guidelines, as well as naming and standardization discussions with PMs. In this document, we have included the main reference and standardization points that were applied during the review and that should be maintained in Admin strings.

    Capitalization

    Only the first letter of buttons should be capitalized.

    Basic UI buttons and terminology

    @@ -102,7 +102,7 @@

    A

    administrador de la tienda

    Always use when referring to the retailer (lojista) in the VTEX Admin.

    anexo

    -

    Use for SKU attachments used to customize products. See documentation.

    +

    Use for SKU attachments used to customize products. See documentation.

    adjunto

    Use for files that will be attached.

    @@ -158,7 +158,7 @@

    L

    M

    máster

    -

    Avoid using. Example: usuario máster was changed to usuario titular.

    +

    Avoid using. Example: usuario máster was changed to usuario titular.

    marketplace

    Do not substitute with any Spanish alternative.

    medio de pago, not método de pago

    @@ -170,7 +170,7 @@

    O

    P

    periodo, not período

    partner, not socio

    -

    Always use partner when referring to VTEX partners, other companies with whom VTEX collaborates. However, you may use asociación to translate partnership. When not referring to VTEX, in a legal context, where they are listing kinds of relationships, you may use socio.

    +

    Always use partner when referring to VTEX partners, other companies with whom VTEX collaborates. However, you may use asociación to translate partnership. When not referring to VTEX, in a legal context, where they are listing kinds of relationships, you may use socio.

    x panel (UI)

    Use dashboard.

    política comercial

    @@ -186,7 +186,7 @@

    R

    S

    x socio

    -

    Always use partner when referring to VTEX partners, other companies with whom VTEX collaborates. However, you may use asociación to translate partnership. When not referring to VTEX, in a legal context, where they are listing kinds of relationships, you may use socio.

    +

    Always use partner when referring to VTEX partners, other companies with whom VTEX collaborates. However, you may use asociación to translate partnership. When not referring to VTEX, in a legal context, where they are listing kinds of relationships, you may use socio.

    seller

    Always use seller when referring to sellers of a marketplace. This is the most frequent case in the Admin. In the inStore app, use vendedor when they refer to a sales associate.

    status

    diff --git a/content/loc_admin_review_logs/Admin String Standardization - PT/VTEXAdminstringstandardizationinPortuguese.html b/content/loc_admin_review_logs/Admin String Standardization - PT/VTEXAdminstringstandardizationinPortuguese.html index fdf6442..ec6a0f1 100644 --- a/content/loc_admin_review_logs/Admin String Standardization - PT/VTEXAdminstringstandardizationinPortuguese.html +++ b/content/loc_admin_review_logs/Admin String Standardization - PT/VTEXAdminstringstandardizationinPortuguese.html @@ -10,7 +10,7 @@

    Padronizações de texto do VTEX Admin para o português

    -

    O VTEX Admin passou por uma revisão integral de seus textos, como proposto no OKR do terceiro trimestre de 2022 de Localization. Nesse processo, aplicamos correções de gramática, tom e voz, visando oferecer uma experiência consistente aos nossos usuários através dos textos mostrados na plataforma. A revisão considerou os padrões já especificados nos guias de estilo de Localization, o glossário de Localization integrado a CAT tool, as UX Writing Guidelines da VTEX, bem como discussões sobre as nomenclaturas e suas padronizações com os PMs responsáveis. Neste documento, organizamos os principais pontos de padronização e preferência aplicados durante a revisão e que devem ser mantidos nos textos do admin.

    +

    O VTEX Admin passou por uma revisão integral de seus textos, como proposto no OKR do terceiro trimestre de 2022 de Localization. Nesse processo, aplicamos correções de gramática, tom e voz, visando oferecer uma experiência consistente aos nossos usuários através dos textos mostrados na plataforma. A revisão considerou os padrões já especificados nos guias de estilo de Localization, o glossário de Localization integrado a CAT tool, as UX Writing Guidelines da VTEX, bem como discussões sobre as nomenclaturas e suas padronizações com os PMs responsáveis. Neste documento, organizamos os principais pontos de padronização e preferência aplicados durante a revisão e que devem ser mantidos nos textos do admin.

    Capitalização

    Sempre usar sentence case para PT, independentemente se for título ou não. Para EN, cada parte da UI tem uma capitalização diferente. Para entendermos cada aplicação, seguimos o guia de UX e o contexto de exibição das frases.

      @@ -79,7 +79,7 @@

      Preferências lexicais

    • A tradução de “returning users” deve ser “usuários recorrentes” (seguindo o padrão do Google Analytics).
    • Utilizamos o termo “upload” também em português.
    • O termo “listagem” deve ser evitado. Para “listing” em inglês, usamos “lista” em português.
    • -
    • because” no meio da frase pode ser traduzido como “porque” ou “pois”, sendo preferencial o primeiro. Se o “porque” for explicativo, deve levar vírgula antes, já se for causal não necessariamente. Nesse caso, o porque causal é uma boa opção para fazer uma frase mais fluida, que não necessita de pausa pela vírgula. Se optar pelo uso de pois, ele deve necessariamente ser precedido por vírgula. Veja aqui alguns exemplos para distinguir o porquê causal do explicativo.
    • +
    • because” no meio da frase pode ser traduzido como “porque” ou “pois”, sendo preferencial o primeiro. Se o “porque” for explicativo, deve levar vírgula antes, já se for causal não necessariamente. Nesse caso, o porque causal é uma boa opção para fazer uma frase mais fluida, que não necessita de pausa pela vírgula. Se optar pelo uso de pois, ele deve necessariamente ser precedido por vírgula. Veja aqui alguns exemplos para distinguir o porquê causal do explicativo.

    Mudanças de terminologia posteriores à revisão do Admin

    Aplicação pendente

    diff --git a/content/loc_style_guides/Localization Style Guide - EN/VTEXLocalizationStyleGuideEN.html b/content/loc_style_guides/Localization Style Guide - EN/VTEXLocalizationStyleGuideEN.html index c44df9e..913e670 100644 --- a/content/loc_style_guides/Localization Style Guide - EN/VTEXLocalizationStyleGuideEN.html +++ b/content/loc_style_guides/Localization Style Guide - EN/VTEXLocalizationStyleGuideEN.html @@ -45,20 +45,20 @@

    British vs. American English

    The standard for content is English - US.

    For example, words that might include either the letter o or the letters ou are written with o (e.g. color, not colour; humor, not humour) and words ending in ze or se should be written with ze (e.g. materialize, not materialise; apologize, not apologise).

    Some Marketing Enablement content is adapted for English - UK.

    -

    For more information, see VTEX Content Styleguide.

    +

    For more information, see VTEX Content Styleguide.

    Gender-neutral language

    You can use the singular they as a generic third-person singular pronoun to refer to a person whose gender is unknown or irrelevant to the context.

    When “they” is the subject of a sentence, “they” takes a plural verb regardless of whether “they” is meant to be singular or plural. For example, write “they are,” not “they is.” The singular “they” works similarly to the singular “you”—even though “you” may refer to one person or multiple people, in a scholarly paper you should write “you are,” not “you is.” However, if the noun in one sentence is a word like “individual” or a person’s name, use a singular verb.

    References:

    -

    MLA Style Center

    -

    APA Style

    +

    MLA Style Center

    +

    APA Style

    Capitalization

    Words, concepts, teams and roles

    As per the VTEX + href="https://docs.google.com/document/d/1gURayqRV2-Cb23_7Z1Isph3KvbVKwl3WvAZe7YX2A34/edit#heading=h.7rfcjkvjmem6">VTEX Content Styleguide:

    The name of the company is in all caps: VTEX.

    Some of our commonly-used words include: marketplace, omnichannel, headless, microservices. Do not capitalize these unless they’re at the beginning of a sentence!

    @@ -73,7 +73,7 @@

    Words, concepts, teams and roles

    Example: Bernardo Lemgruber, Content Marketing Leader, is working within the Marketing Enablement team.

    Document titles and headings

    -

    As per the VTEX Content Styleguide:

    +

    As per the VTEX Content Styleguide:

    Use sentence case. This means only the first word of the title/heading is capitalized (besides other special words that should be capitalized following their own rules – see above section for details).

    Example:

    ✔️ The commerce platform with the fastest growth rate is VTEX, according to IDC

    @@ -92,7 +92,7 @@

    UI and technical texts

    Input, Transitional Text, Confirmation Messages, Alerts, Errors.

    For more information, see the VTEX + href="https://uxwriting.vtex.com/docs/text-patterns/titles">VTEX UX Writing Guidelines.

    Punctuation

    @@ -112,7 +112,7 @@

    Oxford comma

    @@ -138,7 +138,7 @@

    Dash and hyphen

    time or ranges of numbers. To type an en dash, press [Alt+0+1+5+0]. Do not use spaces neither before nor after an en dash.

    Reference: Veeam + href="https://helpcenter.veeam.com/docs/styleguide/tw/dash_hyphen.html">Veeam Technical Writing Style Guide

    Grammar

    @@ -158,10 +158,10 @@

    Indefinite article a/an with SKU

    Pronunciation examples:

    https://www.youtube.com/watch?v=qppwXva8L_Q + href="https://www.youtube.com/watch?v=qppwXva8L_Q">https://www.youtube.com/watch?v=qppwXva8L_Q

    https://www.youtube.com/watch?v=2p-QnvKD-rE + href="https://www.youtube.com/watch?v=2p-QnvKD-rE">https://www.youtube.com/watch?v=2p-QnvKD-rE

    Use of article with proper nouns

    @@ -187,10 +187,10 @@

    Using noun as adjectives (singular)

    References:

    English + href="https://www.englishclub.com/grammar/nouns-adjective.php#:~:text=The%20%22noun%20as%20adjective%22%20is,usually%20in%20the%20singular%20form.&text=In%20other%20words%2C%20if%20there,news%2C%20billiards%2C%20athletics).">English Club

    ESL + href="https://eslgrammar.org/nouns-as-adjectives/">ESL Grammar

    Prepositions

    @@ -198,10 +198,10 @@

    Prepositions

    Prepositions and UI elements

    Useful resources about prepositions and UI elements:

    PEGA + href="https://docs.pega.com/style-guide-content-contributors/other/prepositions-verbs-and-tags-used-user-interface-elements">PEGA Documentation

    The + href="https://books.google.com.br/books?id=V7NWEu_bLXsC&pg=PA214&lpg=PA214&dq=prepositions+used+with+interface+elements&source=bl&ots=N8tyfamrqo&sig=ACfU3U16PZ_62szxbRVvm28kQ9lPeWokQw&hl=en&sa=X&redir_esc=y#v=onepage&q=prepositions%20used%20with%20interface%20elements&f=false">The IBM Style Guide

    Ending a sentence with a preposition

    @@ -211,10 +211,10 @@

    Ending a sentence with a prepositi

    Specify which event hub you want to send the data to.

    References:

    Microsoft + href="https://www.microsoft.com/en-us/microsoft-365-life-hacks/writing/what-is-a-preposition#:~:text=Can%20I%20end%20a%20sentence,sound%20better%20when%20they%20do.">Microsoft blog

    Grammarly + href="https://www.grammarly.com/blog/end-sentence-preposition/">Grammarly

    Log in to vs. Log into

    @@ -231,7 +231,7 @@

    Log in to vs. Log into

  • ✔️ Log in to the machine where Veeam ONE Monitor Client is installed.

Reference: Veeam + href="https://helpcenter.veeam.com/docs/styleguide/tw/log_in_to.html">Veeam Technical Writing Style Guide

Click vs. Click on vs. Click at

@@ -242,7 +242,7 @@

Click vs. Click on vs. Click at

In the Parameter Details column, click the Edit button next to the Default Value field.

To save changes made to the parameter settings, click Save.

Reference: https://helpcenter.veeam.com/docs/styleguide/tw/click.html + href="https://helpcenter.veeam.com/docs/styleguide/tw/click.html">https://helpcenter.veeam.com/docs/styleguide/tw/click.html

On VTEX and at VTEX

@@ -251,16 +251,16 @@

On VTEX and at VTEX

On VTEX, the Google Tag Manager integration is native, which simplifies setting up the tool for analyzing store browsing data.

Examples from other companies

https://learn.microsoft.com/en-us/azure/architecture/example-scenario/apps/sap-production + href="https://learn.microsoft.com/en-us/azure/architecture/example-scenario/apps/sap-production">https://learn.microsoft.com/en-us/azure/architecture/example-scenario/apps/sap-production

https://www.shopify.com/online-store + href="https://www.shopify.com/online-store">https://www.shopify.com/online-store

https://www.zoho.com/index1.html + href="https://www.zoho.com/index1.html">https://www.zoho.com/index1.html

https://access.redhat.com/articles/6093611 + href="https://access.redhat.com/articles/6093611">https://access.redhat.com/articles/6093611

When referring to VTEX as a company, use at VTEX.

Examples:

@@ -268,10 +268,10 @@

On VTEX and at VTEX

At VTEX, we follow the most effective security practices.

Examples from other companies

https://blog.google/inside-google/life-at-google/ + href="https://blog.google/inside-google/life-at-google">https://blog.google/inside-google/life-at-google/

https://shopify.engineering/work-with-us + href="https://shopify.engineering/work-with-us">https://shopify.engineering/work-with-us

In Checkout and at checkout

@@ -373,7 +373,7 @@

Compound and hyphenated words

fastest-growing platform; world-class retailer; user-friendly UX, etc.

Reference: VTEX + href="https://uxwriting.vtex.com/docs/text-patterns/titles">VTEX UX Writing Guidelines

Contractions

@@ -410,7 +410,7 @@

Numbers

✔️ Half / Fifty percent of the shoppers have opted for pick-up in-store.

✘ 50% of shoppers have opted for pick-up in-store

Reference: VTEX + href="https://uxwriting.vtex.com/docs/text-patterns/titles">VTEX UX Writing Guidelines

Currency

@@ -425,7 +425,7 @@

Currency

✔️ £20

✔️ €20

Reference: VTEX + href="https://uxwriting.vtex.com/docs/text-patterns/titles">VTEX UX Writing Guidelines

Dates

@@ -438,7 +438,7 @@

Dates

How fortunate that the world did not end on Friday, December 21, 2012!

Monday, May 5, is my last day of work.

Reference: Grammarly + href="https://www.grammarly.com/blog/how-to-write-dates/">Grammarly

Time format

@@ -447,10 +447,10 @@

Time format

When a time is giving in Brazil time, include the GMT format.

Example: 10:30 a.m São Paulo (GMT-3).

For more information about time zones, see this article. + href="https://editorsmanual.com/articles/time-zones/#daylight-saving">article.

Reference: Western + href="https://wmich.edu/writing/rules/times">Western Michigan University Writing Style Guide

Symbols

@@ -461,10 +461,10 @@

Symbols

References:

https://www.quickanddirtytips.com/articles/units-of-measure/ + href="https://www.quickanddirtytips.com/articles/units-of-measure/">https://www.quickanddirtytips.com/articles/units-of-measure/

https://docs.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/term-collections/bits-bytes-terms + href="https://docs.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/term-collections/bits-bytes-terms">https://docs.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/term-collections/bits-bytes-terms

Percent and percentage

@@ -480,8 +480,8 @@

Percent and percentage

  • What percentage (not per cent) of your company’s employees work flexible hours?
  • References:

    -

    ​​https://www.btb.termiumplus.gc.ca/tpv2guides/guides/wrtps/index-eng.html?lang=eng&lettr=indx_catlog_p&page=9TeYbIhQbfVM.html

    -

    https://www.crowdcontent.com/blog/writers-hub/ap-style-percent-formatting/

    +

    ​​https://www.btb.termiumplus.gc.ca/tpv2guides/guides/wrtps/index-eng.html?lang=eng&lettr=indx_catlog_p&page=9TeYbIhQbfVM.html

    +

    https://www.crowdcontent.com/blog/writers-hub/ap-style-percent-formatting/

    https://www.chicagomanualofstyle.org/qanda/data/faq/topics/Numbers/faq0024.html

    Specific subjects

    @@ -513,7 +513,7 @@

    According to

    Source: Macmillan + href="https://www.macmillandictionary.com/us/dictionary/american/used">Macmillan Dictionary

    Try to use based on or depending on as much as possible.

    Examples:

    @@ -541,7 +541,7 @@

    Amount and value

    Data (Singular usage)

    Treat “data” as a singular noun.

    Reference: https://developers.google.com/style/word-list#letter-d + href="https://developers.google.com/style/word-list#letter-d">https://developers.google.com/style/word-list#letter-d

    Usage Note: The word data is the plural of Latin datum, "something given." In English, most notably in scientific usage, this plural usage is still common, as in this example: @@ -557,7 +557,7 @@

    Data (Singular usage)

    facts or results.) The percentages in the 2005 survey represent significant increases over those of our 1988 survey, making it safe to say that singular data has become a standard usage.

    Reference: https://www.thefreedictionary.com/data + href="https://www.thefreedictionary.com/data">https://www.thefreedictionary.com/data

    Ecommerce

    @@ -569,7 +569,7 @@

    Ecommerce

    ✘ Ecommerce*

    ✘ Any other variant our creative minds might come up with

    Reference: VTEX + href="https://uxwriting.vtex.com/docs/text-patterns/titles">VTEX UX Writing Guidelines

    "For example" at the end of the sentence

    @@ -578,9 +578,9 @@

    "For example" at the end of the example can follow nouns or noun phrases, verbs, or dependent clauses, and, therefore, be in the middle of a sentence.

    Reference: ‘For + href="https://open.library.okstate.edu/internationalcomposition/chapter/for-example-inside-a-sentence/">‘For example’: Inside a Sentence + href="https://open.library.okstate.edu/internationalcomposition/chapter/for-example-inside-a-sentence/">

    When translating, for example can be placed at the beginning or in the middle of the sentence, and sometimes even omitted. Also, such as is a good option to introduce examples at the end of a sentence.

    Examples:

    @@ -619,9 +619,9 @@

    Plural of status

    Example:

    Possible statuses include: "open" and "blocked".

    References:

    -

    What is the plural of status?

    -

    Status (The Free Dictionary)

    -

    External examples: Microsoft, Google

    +

    What is the plural of status?

    +

    Status (The Free Dictionary)

    +

    External examples: Google

    Step-by-step

    In English, step-by-step is an adjective phrase and requires a noun to convey a complete thought. Never use on its own. Often passo a passo can be translated simply as instructions or guide, especially if it’s the title of a section.

    Examples:

    @@ -723,7 +723,7 @@

    Currency and symbols

    Examples:

    The amount required is EUR 500

    A sum of USD 300 was spent

    -

    You can find an exhaustive list of codes here.

    +

    You can find an exhaustive list of codes here.

    Numbering system

    When the following numbering styles are used in the original text, they should be used in the translation:

    @@ -745,7 +745,7 @@

    Abbreviations

    A commonly used abbreviation used in the signing section at the end of contracts is “attn.” + href="https://www.ldoceonline.com/dictionary/attn">attn.” and it means “for the attention of”. Please make sure it is abbreviated correctly.

    @@ -849,19 +849,19 @@

    Equivalences

    Resources

    -

    VTEX UX Writing Guidelines

    -

    Marketing Localization Guidelines

    -

    VTEX Help Center

    -

    Admin/Stores: Different Admin versions are available. Please always confirm with the writer which store they used as a reference. Here are two main ones: cosmetics2 (Admin V3), storecomponents (Admin V4).

    -

    Microsoft Writing Style Guide

    -

    Veeam Technical Writing Style Guide

    -

    IATE - EU Terminology Base

    -

    Legal Glossary

    -

    EU List of countries, territories and currencies

    -

    Bilingual Dictionary of Legal and Business Terms

    -

    Diccionario Politécnico de las Lenguas Española e Inglesa

    +

    VTEX UX Writing Guidelines

    +

    Marketing Localization Guidelines

    +

    VTEX Help Center

    +

    Admin/Stores: Different Admin versions are available. Please always confirm with the writer which store they used as a reference. Here are two main ones: storecomponents (Admin V4).

    +

    Microsoft Writing Style Guide

    +

    Veeam Technical Writing Style Guide

    +

    IATE - EU Terminology Base

    +

    Legal Glossary

    +

    EU List of countries, territories and currencies

    +

    Bilingual Dictionary of Legal and Business Terms

    +

    Diccionario Politécnico de las Lenguas Española e Inglesa

    Topics:

    -

    Prepositions in the end of the sentence

    +

    Prepositions in the end of the sentence