B Edit

back end, back-end

Two words as a noun, hyphenate as an adjective.

Avoid using if you can use a contextually relevant term such as database, server, or operating system.

Top ↑

One word. Not back link or back-link.

Top ↑

backslash

One word. Not back slash or back-slash.

Use backslash to describe the \ character.

Top ↑

backspace

One word. Not back space or back-space.

It’s OK to use backspace as a verb.

Top ↑

backup, back up

Two words as a verb, one word as an adjective or a noun.

Not back-up.

Top ↑

backward compatible

Not backwards compatible or backwards compatibility.

Top ↑

bandwidth

One word. Not band width or band-width.

Top ↑

bar

Avoid using. Instead, use a clearer and more meaningful placeholder with relevant text.

For more information, see Placeholders.

See also foo, foobar, fubar.

Top ↑

-based

In general, hyphenate compound adjectives ending with -based such as ARM-based, application-based, and HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites.-based.

Use an en dash if based follows a term with two or more words.

Example

Recommended: ARM processor–based device

For more information, see Hyphens and Dashes.

For word usage of specific terms, see The American Heritage Dictionary.

Top ↑

bbPress

Use lowercase for bb. Capitalize P.

Not Bbpress, Bb press, Bb Press, bb press or bbpress.

Exception: It is OK to use bbpress in lowercase in developer documentation such as commands, or WordPress URLs. For example, codex.bbpress.org/.

Top ↑

because

Use because to mean for the reason that.

See also since.

Top ↑

below

Don’t use to mean later to refer to a position in a document or article. Instead, use following.

Don’t use as an adjective to introduce a table, list, or other content as in the below section. Instead, use the following or use a cross-reference.

For more information, see Cross-references.

Don’t use to refer to a position in the UI. In general, avoid using directional language in instructions to locate UI elements or other content. Directional language proves to be difficult for accessibility or for localization. People with cognitive impairments, as well as people using assistive technologies such as screen-reading software and might have difficulty interpreting directional language. If a particular UI element or other content is difficult to convey, include a screenshot or illustration.

For more information, see Procedures and instructions.

See also following.

Top ↑

beta

Capitalize when part of a product name.

Examples

Recommended: WordPress 5.8 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 4

Recommended: WordPress has released a betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. version of 5.8.

Top ↑

between

Use between when referring to two or more distinct things.

Example

Recommended: These are the main differences between WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/ and WordPress.

Don’t interchange between with among. Use among when referring to two or more things that aren’t distinct.

See also among.

Top ↑

bi-

In general, don’t hyphenate words beginning with bi- such as bimodal, biweekly, and bidirectional, unless bi- is followed by a proper noun or it is absolutely necessary to avoid confusion.

For more information, see Hyphens.

For word usage of specific terms, see The American Heritage Dictionary.

Top ↑

billion, B

Don’t abbreviate billion as B, b, or bn. Spell out the word or denote the entire number.

For more information, see Abbreviations.

Top ↑

bit

Shortened term for binary digit.

Hyphenate as an adjective.

Examples

Recommended: AES provides 128-bit, 192-bit or 256-bit encryption.

Recommended: Copy the 32-bit key.

Recommended: The key uses 32 bits.

Top ↑

bitmap

One word. Not bit map or bit-map.

Don’t use generically to refer to any graphic. Instead, use illustration, picture, image, figure, or a contextually relevant term instead.

Top ↑

bps (bit/s), bits per second

Initialism for bits per second.

For more information, see Units of measurement.

For more information about spelling out abbreviations, see Abbreviations.

See also bit.

Top ↑

black box

Don’t use. Instead, use closed, closed box, opaque testing, or a contextually relevant term.

For more information, see Writing inclusive documentation.

Top ↑

blacklist, black list, black-list

Don’t use. Instead, use deny list, blocklist, disallowed, unapproved, or a contextually relevant term.

For more information, see Replacing established terms.

Top ↑

blank

Don’t use as a verb to mean removing the contents of any element. Instead, use clear.

See also clear.

Top ↑

blog

Shortened term for weblog. Always use blog.

Don’t use blog as a verb. Instead, use write, publish, or a contextually relevant term.

Top ↑

bold

Use only as an adjective, not as a noun or verb.

Don’t use bolded, boldface, or boldfaced.

For more information, see Text highlighting.

Top ↑

bookmark

One word. Not book mark or book-mark.

Top ↑

Boolean

Capitalize.

Top ↑

boot

Don’t use as a verb to mean turning on a device. Instead, use turn on.

It’s OK to use boot in developer documentation and for a technical audience.

See also turn on, turn off.

Top ↑

bottom left, bottom right

Don’t use.

See lower left, lower right.

Top ↑

box

In general, emphasize on the task to be accomplished, rather than how the user should interact with the UI element. Refer to a box by its label instead of field. If you have to use a descriptor, use the complete term such as list box or checkbox.

Don’t use dialog box. Instead, use dialog.

For more information, see UI elements.

See also checkbox, dialog.

Top ↑

brackets

See brackets.

Top ↑

browse

Use to refer to manually scanning internet sites or other files.

It’s OK to use browse as either a transitive verb, as in browse the web or an intransitive verb, as in browse through a document.

Top ↑

BuddyPress

Capitalize B and P.

Not Buddypress, Buddy press, Buddy Press, or buddypress.

Exception: It is OK to use buddypress in lowercase in developer documentation such as commands, or BuddyPress URLs. For example, codex.buddypress.org/.

Top ↑

bug

OK to use in developer documentation and for a technical audience. Avoid using in user documentation and for a general audience.

Instead, use problem, condition, issue, or situation.

Top ↑

build

It’s OK to use build in developer documentation and for a technical audience as a verb to mean compile and as a noun to mean version.

Avoid using in user documentation and for a general audience as a synonym for create, make or develop. Instead, use a contextually relevant term.

Top ↑

built-in

Hyphenate as an adjective.

Top ↑

button

In general, emphasize on the task to be accomplished, rather than how the user should interact with the UI element. Refer to a button by its label. If you have to use a descriptor, use button.

For more information, see Button and icon.

Last updated: