A
a.m., am
Write AM instead of "a.m." or "am". See Date and time.
above
Don't use directional language (above, below, left, right) as it isn't accessible. See Inclusive Language and Accessibility.
add
Use "add" when adding an existing object to a list. Don't use "add" to mean "create".
and/or
Don't use "and/or" unless it's absolutely necessary to save space. Most of the time, it's appropriate to use "or" on its own.
B
back
Use "back" to describe going to the previous step in a multi-step process.
below
Don't use directional language (above, below, left, right) as it isn't accessible. See Inclusive Language and Accessibility.
blacklist
Use “blocklist” instead.
button
For the most part, avoid referring to parts of the UI. If you need to refer to a specific button, use the button's label without calling it a button.
It can be clearer to include the word "button" when talking about buttons that don't have labels, like "the Minimize button". Don't capitalize "button".
C
cancel, canceled, canceling
Use "cancel" to describe ending a process or an action. Do not use "cancel" to describe closing a non-editable window. Use "close" instead.
Spell "canceled" and "canceling" with one "l".
choose
Use "choose" to refer to generic user decisions that don't specifically involve the UI. Use "select" when referring to specific UI elements that the user clicks or taps.
For example, "choose your notification preferences" vs "select Send daily email".
click, double-click
Don't use "click" or "double-click" to describe user actions. Use "select" instead. See Inclusive Language and Accessibility.
close
Use "close" to describe closing a non-editable window.
To describe ending an action or process, which may also close the window, use "cancel'. To confirm the completion of a task where the changes have already been saved, use "done".
continue
Don't use "continue" to describe progressing to the next step in a multi-step process. Use "next" instead.
create
Use "create" to describe creating a new object.
D
delete
Use "delete" to describe removing something from the system, like a report or a tactic. Don't use "delete" to mean "remove", which describes taking an object off of a list.
disable, disabled
Avoid using disable. Use a more specific term, like “turn off” or “unavailable”.,
Don’t say “disabled”. Instead, say “unavailable” or another similar term.
done
Use "done" to confirm the completion of a task where changes have already been saved.
To describe closing a non-editable window, use "close". To describe ending an action or process, which may also close the window, use "cancel'.
E
enable
Avoid using enable. Use “turn on” or “allow”, or a more specific term that better describes the action or the state of the feature.
It is okay to use “enable” in certain technical settings, but it should be avoided in the UI.
Avoid “enabled”. Say “available” or something similar instead.
F
G
H
Help Center
When referring to the Basis Help Center, use "Help Center". Capitalize both words. Don't use "User Guide", "Basis Support", or another term.
I
J
K
L
left
Don't use directional language (above, below, left, right) as it isn't accessible. See Inclusive Language and Accessibility.
M
N
next
Use "next" to progress to the following step of a multi-step process.
O
once
Don't use "once" instead of "when" or "after". For example, say "Save your work when you're done." instead of "Save your work once you're done."
online
Write "online" as one word.
P
p.m., pm
Write PM instead of "p.m." or "pm". See Date and time.
please
Avoid saying "please". Reserve it for instances where there was a major error on our end or if you're asking the user to do something inconvenient. See Error Handling.
previous
Don't use "previous" to describe going to the previous step in a multi-step process. Use "back" instead.
Q
quit
Avoid using "quit" to refer to closing a modal or ending an action. Use "close", "cancel", or "log out" instead.
R
remove
Use "remove" to describe removing an object from a list. Don't use "remove" to mean "delete".
right
Don't use directional language (above, below, left, right) as it isn't accessible. See Inclusive Language and Accessibility.
S
(s), (es)
Don’t use (s) or (es) to show that something could be plural. Just use the plural instead. If it’s absolutely necessary to show that something could be singular or plural, use “one or more.”
For example, instead of “Select deal(s)”, say “Select deals” or “Select one or more deals”.
see
Use “see” to direct the user to more information. For example, “see details”, “see more”, “see [Help Center Page]”.
select
Use "select" to describe the user action of selecting a button, a menu option, a checkbox, and so on. "Select" is a generic term that can refer to any input method. Don't use "click", "tap", or other device-specific terms. See Inclusive Language and Accessibility.
since
It is often correct to use "because" instead of "since". "Since" is ambiguous and often refers to the passage of time. "Because" only has one meaning, referring to cause and effect.
T
tap, double-tap
Don't use "tap" or "double-tap" to describe user actions. Use "select" instead. See Inclusive Language and Accessibility.
U
utilize
Say “use” instead.
V
view
It’s okay to use “view”, but it’s often better to say “see” instead because view could be interpreted as a noun (such as “Grid view”).
W
whitelist
Use “allowlist” instead.
X
Y
Z
ZIP, ZIP code
When you have to specifically refer to the US, it's okay to use "ZIP" or "ZIP code". For a general audience, use "postal code" instead.
Always capitalize every letter in "ZIP".