Skip to main content
Elastic UI
Elastic UI
ComponentsPatternsContentData visualization
EUI ChangelogGitHubFigma
  • Content
  • Voice and writing style
  • Tone
  • Language
  • Accessibility
  • Inclusivity
  • Word choice
  • EUI
  • Word choice

Word choice

Find the right term to use in your UI copy.

Use these preferred words and terms

Use these words and terms in the scenarios described in the following table:

WordUsage notes
addUse for establishing a new relationship. Often used in create-then-add scenarios. Create a dashboard, then add a visualization. In button labels, always follow add by an object. Remove is the correct opposite.
cancelUse to stop an action without saving pending changes.
can'tUse to indicate you don't have the ability to do something. Often confused with unable.
createUse for creating an object from scratch. In button labels, always followed by an object. Do not use create new. Delete is the correct opposite.
deleteUse when deleting data that users can no longer retrieve. Create is the correct opposite.
editDon't use change or modify. Edit is the better choice for localization.
enterUse when the user enters text. Don't use type.
laterUse when referring to versions of the product. For example, Elastic Stack 8.13 and later.
openUse when opening an application or program. Don't use launch.
pressUse press for keyboard keys. Don't use hit.
removeUse when removing a relationship, but not permanently deleting the data. For example, you remove a visualization from a dashboard. Add is the correct opposite.
selectSelect is preferred over choose.
useUse instead of utilize and make use of.
viewUse instead of see because view is more inclusive.

Avoid these words and terms

This section includes terms that you should avoid in most instances. These terms might be offensive, non-inclusive, unclear, or unnecessary. Use the alternate suggestions in the following tables or a more specific term.

Latin abbreviations

Latin abbreviations can be unclear. Use the following suggestions instead:

WordUsage notes
e.g.Use for example or such as instead.
i.e.Use that is instead.
viaUse with, by using, or through instead.

Directional language

Directional language does not meet accessibility requirements and you should avoid it, especially as the only way to find an element in the UI. Use the following suggestions instead:

WordUsage notes
aboveUse a link, previous, or preceding instead.
belowUse a link or following instead

Nouns created from verbs

Avoid using nouns created from adjectives or verbs. These words often make text unnecessarily complex. For example:

  • Use choose instead of make a choice.
  • Use register instead of complete your registration.
  • Use investigate instead of conduct an investigation.

General words and terms to avoid

Avoid the following words and terms, and use the suggestions instead:

WordUsage notes
abortUse shut down, cancel, or stop instead.
as well asUse and instead.
blacklistUse blocked list instead.
bootUse start or run instead.
bottom left, bottom rightUse lower left or lower right instead. Hyphenate when using as an adjective. For example, lower-left corner.
chooseUse select instead. See Words for interacting with UI
disableUse turn off, block, or hide.
enableUse turn on or allow.
easy, easilyIt can be frustrating for users to think that something is easy, but then struggle to do the task. Typically the same meaning can be conveyed without this word.
executeUse run or start instead.
hackFor a noun, use tip or work-around instead. For a verb, use configure or modify.
hitFor a noun, use visits (as in web visits). For a verb, use select or press.
hear, hear aboutUse learn instead.
impactDon't use impact as a verb. Use affect instead.
in order toUse simple verbs like to instead.
invalidUse not valid or incorrect instead.
justDon't use before a command, like "just click here."
launchUse open instead.
okDon't use when labeling buttons. Use words that explain the action instead, for example, Delete rule.
normal, normallyUse usual or typical instead. For normally, use usually, typically, or generally instead.
pleaseIn most cases, please is unnecessary. Only use when the user must wait or do something inconvenient.
simple, simplyUnnecessary because it doesn't add any information or value.
sorryOnly use sorry in error messages that cause serious problems for the user.
successUnnecessary because success is generally implied.
terminateUse stop or exit instead.
typeUse enter because there is typically more than one way to enter text.
top left, top rightUse upper left or upper right instead. Hyphenate when using as an adjective. For example, upper-left corner.
utilizeDon't use utilize when you mean use.
whitelistUse allow list instead.

Use caution with these words and terms

These words and terms might be appropriate in some situations and inappropriate in others. Only use them when appropriate.

WordUsage notes
app, applicationUse only when needed for clarity. Otherwise, a Kibana application name can stand alone. App is a well-known abbreviation for application and is preferred.
beginUse context to decide between begin and start. For example, begin a procedure, begin an analysis, or begin an installation are common phrases. Similarly, start a program, start an engine, or start a timer are frequently used. Start is considered less formal than begin. End is the correct opposite of begin.
canUse for capability. Rewrite as an action if possible. For example, instead of you can add... use add....
clickAcceptable to use when describing mouse actions. Otherwise, use verbs that work with multiple devices, such as select.
cloneUse when creating a copy that is linked to the original. Often confused with copy and duplicate.
copyUse when the file is added to a clipboard and can be pasted in a new location. Often confused with clone and duplicate.
disableDon't use to describe something that is broken. Use inactive, unavailable, deactivate, turn off, or deselect, depending on the context.
duplicateUse when immediately creating a copy of an object in the same location as the original. Often confused with copy and clone.
killUse cancel or stop unless the actual command is kill.
mayUse may for permissibility. Use can for capability. Use might for possibility.
startUse context to decide between start and begin. For example, start a program, start an engine, or start a timer are common phrases. Similarly, begin a procedure, begin an analysis, or begin an installation are frequently used. Start is considered less formal than begin.
unableUnable means not being able to perform an action. Often confused with cannot.
Edit this page

Previous
Inclusivity
  • Use these preferred words and terms
  • Avoid these words and terms
    • Latin abbreviations
    • Directional language
    • Nouns created from verbs
    • General words and terms to avoid
  • Use caution with these words and terms
EUI is dual-licensed under Elastic License 2.0 and Server Side Public License, v 1 | Crafted with ❤ by Elastic