> Markdown version of [Word List](https://vaadin.com/docs/v23/contributing-docs/style-guide/word-list). Section index: [llms.txt](https://vaadin.com/docs/v23/contributing-docs/llms.txt)

# Word List

<!-- vale Vaadin.HeadingCase = NO --><!-- vale Vaadin.Abbr = NO --><!-- vale Vaadin.FirstPerson = NO --><!-- vale Vaadin.We = NO --><!-- vale Vaadin.Wordiness = NO --><!-- vale Vaadin.TooWordy = NO --><!-- vale Vaadin.Terms = NO -->

## <a id="word-list-and-quick-reference"></a>Word List and Quick Reference

## <a id="miscellaneous-terms"></a>Miscellaneous Terms

### <a id="3d"></a>"3D"

Abbreviation of *three dimensions* or *three-dimensional*.\
**Not** *3-D*.\
For example:

The image is visible in *3D*. The system displays a *3D* image.

## <a id="a"></a>A

### <a id="word-list.a_an"></a>"a", "an"

The choice of whether to use *a* or *an* depends on the **sound** of the following element, not purely on whether that element begins with a vowel.

If the **sound** of the next item is a vowel sound, use *an*; otherwise, use *a*.\
For example:

*She decided to do **a** university course.*\
\[*University* begins with a consonant sound.]

*It was **an** unusual choice.*\
\[*Unusual* begins with a vowel sound.]

*We stayed in **a** hotel on the Left Bank.*\
\[*Hotel* begins with a consonant sound.]

*It was **an** honest mistake.*\
\[*Honest* begins with a vowel sound.]

The same principle applies to acronyms.

Decide on how the acronym is usually read – as a word or as individual letters – and select *a* or *an* based on the resulting initial sound.

For example:

*The product comes from **a** US company.*

<!-- vale Vale.Spelling = NO -->

*Send me **an** SMS when you are ready.*\
\[*SMS* is read as *ess\_em\_ess*, so it begins with a vowel sound.]

<!-- vale Vale.Spelling = YES -->

*He is a former member of **a** SWAT team.*\
\[*SWAT* is generally pronounced as one word – *swat*.]

### <a id="above"></a>"above"

Don’t use *above* to indicate the position of an item on a page. Various devices, screen readers and browsers may position elements in different places. Instead, use *previous* or *earlier*.

### <a id="add-in"></a>"add-in"

### <a id="add-on"></a>"add-on"

### <a id="advice"></a>“advice”

"Advice" is an uncountable noun. For that reason, it can’t be used with the indefinite article (*an advice*) and it can’t be plural (*advices*).\
If you want to use the indefinite article, you need to introduce another word, such as *piece* or *bit*. For example:

*The developer gave me a good **piece of advice**.*

You can use quantifier phrases such as *some* and *a lot of*.\
For example:

*The user guide contains **a lot of good advice**.*

### <a id="agnostic"></a>"agnostic"

This term is sometimes used to indicate the absence of a dependence on some other software component, such as an operating system or platform.\
It’s better to use a clearer term, such as *platform-independent*.

### <a id="aka"></a>"aka"

This is an abbreviation of *also known as*. It has its origins in police usage and, hence, conveys an inappropriate tone for software documentation.

Instead, use parentheses or the word *or*.\
For example:

*The company specializes in software as a service **(SaaS)**.*\
*Each instantiated object of the class has a separate copy, **or instance**.*

### <a id="a-m-p-m"></a>"a.m.", "p.m."

Write these in lower case, with periods. Insert a non-breaking space (`&nbsp;` in AsciiDoc) between the time in numerals and *a.m.* or *p.m.*\
For example:

*The meeting started at 9∶15 about **a.m**.*\
*We received the email at 5∶00 **p.m.** yesterday.*

### <a id="alright"></a>"alright"

Avoid using *alright*.\
Instead, use *all right*.

### <a id="alternate-alternative"></a>"alternate", "alternative"

*Alternate* is a verb that describes something that switches repeatedly between two states, or conveys the concept of *every other*.

*Alternative* is a noun or an adjective that indicates two possible options.\
For example:

*The weather **alternated** between sunny and cloudy.*

*An **alternative** to installing the software using a package manager is to download it as an AppImage.*

### <a id="america"></a>"America"

Don’t use *America* or *American* as synonyms for *United States* or *US*. In general, use *US*, as both a noun and an adjective.

*If you live in the **US**, contact our San Francisco support desk.*

*You need to comply with **US** data protection legislation.*

### <a id="ampersand"></a>ampersand ("&")

Don’t use the ampersand character in place of *and* in general text, unless space is limited.

### <a id="andor"></a>"and / or"

Insert a non-breaking space (`&nbsp;` in AsciiDoc) before and after the slash ("/") character in *and / or*.

See [slash ("/")](https://vaadin.com/docs/v23/contributing-docs/style-guide/style.md#a_to_z.slash).

### <a id="anti-malware"></a>"anti-malware"

### <a id="antialiasing"></a>"antialiasing"

### <a id="antivirus"></a>"antivirus"

### <a id="app"></a>"app"

Use *application*, rather than *app*.

### <a id="approximately"></a>"approximately"

Write this in full; don’t use *approx*.

### <a id="word-list.as_if_or_like"></a>"as if" or "like"?

Consider this sentence:

*It looks as if it’s going to rain.*

Here, the clause *it’s going to rain* contains a finite (complete) verb (*is going to rain*).

In this situation, we should use *as if* to connect the two parts of the sentence. It isn’t correct to say, *It looks like it’s going to rain*, although this is a very common grammatical error.

Here is another sentence:

*It looks like rain.*

Here, the noun phrase *rain* doesn’t contain a finite verb. In this situation, we should use *like* to connect the two parts of the sentence.

Another way of thinking of this is to say that *as if* "expects" to be followed by a verb clause. In contrast, the word *like* "expects" to be followed by a noun or a noun phrase.

Some other examples:

*Treat the issue **as if** it were a bug.*\
\[Verb clause]

*They treated me **like** a VIP.*\
\[Noun phrase]

### <a id="word-list.as_or_like"></a>“as” or “like”?

*As* "expects" to be followed by a verb clause.\
Instead, *like* "expects" to be followed by a noun phrase (that is a phrase that has the grammatical function of a noun).\
For example:

*Edit the file **as** you would normally.*\
\[Not *like you would*.]

*Make the amendments **as** described below.*\
\[Not *like described*.]

***As** I have already mentioned, the software is open source.*\
\[Not *like I have already mentioned*.]

### <a id="as-such"></a>"as such"

*As such* does **not** mean *for that reason*.

Instead, it means *in its role as the previously mentioned thing*.\
For example:

*This software is the most capable of its peer group and, **as such**, is an excellent buy.*\
\[That is, *as the most capable of its peer group…*.]

*I was the chief designer on this project and, **as such**, I take full responsibility for design defects.*\
\[That is, *as the chief designer…*.]

*As such* is often incorrectly used in place of phrases like *so* or *consequently*. Here are some examples of **incorrect** usage:

*Developers appreciate the convenience of the toolkit and, as such, it’s a popular choice.*\
\[Incorrect]

*The team were in a hurry to complete the project and, as such, made several poor decisions.*\
\[Incorrect]

### <a id="ascii"></a>"ASCII"

### <a id="aspect-ratio"></a>"aspect ratio"

### <a id="assembly-language"></a>"assembly language"

Use *assembly language*, not *assembler*.

### <a id="asynchronous"></a>“asynchronous”

The adjective is *asynchronous*. The adverb is *asynchronously*.\
Don’t use *async*.

### <a id="authenticate"></a>"authenticate"

### <a id="auto"></a>"auto-"

No general rule exists on whether to hyphenate a word that begins with the prefix *auto-*.\
It’s best to check in the dictionary.

If the word isn’t given either in this guide or in the Merriam-Webster online dictionary, don’t invent it yourself; use another term, for example with the adverb *automatically*.

### <a id="autosave"></a>"autosave"

### <a id="awesome"></a>“awesome”

In its literal meaning, *awesome* is used to describe something that causes awe, a feeling of respect blended with fear or wonder.

*The launch of the huge rocket on a pillar of smoke and flames was an awesome sight.*\
*The enormously powerful waterfall is really an awesome spectacle.*

In modern informal speech, *awesome* has been diverted from its literal meaning to be a synonym for *very good*.\
Avoid this usage in technical documentation.

## <a id="b"></a>B

### <a id="back-button"></a>"back button"

### <a id="backup-back-up"></a>"backup", "back up"

The noun and adjective are *backup*. The verb is *to back up*. For example:

*Confirm that the **backup** completed successfully.*\
\[Noun]

*It’s vital to have reliable **backup** procedures in place.*\
\[Adjective]

*You should back up all your files regularly.*\
\[Verb]

*The data is subsequently **backed up** to the cloud.*\
\[Verb]

### <a id="backend"></a>“backend”

### <a id="backward-compatibility"></a>"backward compatibility"

The noun is *backward compatibility*. The adjective is *backward-compatible*.

### <a id="backspace"></a>"backspace"

### <a id="bandwidth"></a>"bandwidth"

### <a id="base64"></a>"base64"

### <a id="below"></a>"below"

Don’t use *below* to indicate the position of an item on the screen, as different devices and browsers may position elements differently.

Consider using *later* or *in the following*.

### <a id="beta"></a>"beta"

The word *beta* should be written in lowercase, unless it appears differently as part of a defined product name.

### <a id="big-data"></a>"big data"

The noun phrase is *big data*. The adjective phrase is *big-data*.

### <a id="big-endian"></a>"big-endian"

### <a id="blacklist"></a>"blacklist"

Don’t use the term *blacklist*. Instead, use *deny list*.\
The opposite is *allow list*, not *whitelist*.

### <a id="blind"></a>"blind"

Avoid using *blind* in an idiomatic or metaphorical sense.

To refer to people, use, for example, *a blind person* or *a visually impaired person* (whichever is more accurate in the context).

See also [color blind](#word-list.color_blind).

### <a id="bluetooth"></a>"Bluetooth"

*Bluetooth* is a proper noun, so it should be capitalized.

### <a id="boolean"></a>"Boolean"

Capitalize *Boolean* in general use.

### <a id="bot"></a>"bot"

### <a id="both"></a>“both”

"Both" is an emphatic word that applies specifically to two stated things.\
It can’t be used for more than two.\
For example:

*This functionality is available in both Eclipse and NetBeans.*

It’s incorrect to say, for example:

*This functionality is available in both Eclipse, NetBeans, and IntelliJ IDEA.*

To apply similar emphasis to more than two things, it would be necessary to say something like:

*This functionality is available in all of Eclipse, NetBeans, and IntelliJ IDEA.*

However, it might be more elegant to say, for example:\
*Eclipse, NetBeans, and IntelliJ IDEA all have this functionality.*

### <a id="breakpoint"></a>"breakpoint"

### <a id="browsable"></a>"browsable"

### <a id="built-in"></a>"built-in"

The adjective is *built-in* when it’s used attributively (that is, **before** the noun that it describes).\
When it’s used predicatively (that is, **after** a verb such as *be*, *seem*, *look*), the adjective phrase is *built in*. For example:

*The device has a **built-in** DVD drive.*\
\[The adjective is used attributively.]

*The DVD drive is **built in**.*\
\[The adjective is used predicatively.]

*The device has a DVD drive **built in**.*\
\[The adjective is used predicatively.]

## <a id="c"></a>C

### <a id="cache-cached-caching"></a>"cache", "cached", "caching"

### <a id="callback-call-back"></a>"callback", "call back"

The noun and adjective are *callback*. The verb is *call back*.

### <a id="call-out-call-out"></a>"call-out", "call out"

The noun and adjective are *call-out*. The verb is *call out*.

### <a id="cancel"></a>"cancel"

*canceled*, *canceling*, *cancellation*.

### <a id="catalog"></a>"catalog"

<!-- vale Vaadin.EN_US = NO -->

Use *catalog*, not *catalogue*.

<!-- vale Vaadin.EN_US = YES -->

### <a id="cell-phone"></a>"cell phone"

Don’t use *cell phone*.\
Instead, use *mobile* or *mobile phone*.

### <a id="cent"></a>"cent"

The *cent* symbol (*¢*) can be written as `&cent;` in AsciiDoc.

### <a id="chat"></a>"chat"

*Chat* may refer to different activities, depending on the context.\
Use *chat* to refer to exchanging text messages in real time, if the context makes the meaning clear.\
Use *voice chat* to refer to communicating by voice.

### <a id="check"></a>"check"

Don’t use *check* to refer to selecting a checkbox in the user interface.\
Instead, use *select*.

### <a id="check-mark"></a>"check mark"

In the UI, a *check mark* is a visual indication that an item is selected.

### <a id="checkbox"></a>"checkbox"

The spelling is *checkbox*.

Use *select* and *clear* to refer to user interaction with checkboxes.

### <a id="click"></a>"click"

*Click* is both a verb and a noun.\
More-specific variants are *left-click*, *right-click*, and *double-click* (all hyphenated).\
For example:

*Enter the required details and **click** OK.*

***Right-clicking** on the drop-down presents the user with more options.*

### <a id="client-side"></a>“client side”

When used as a noun phrase, *client side* has no hyphen:

*The validation is handled on the client side.*

When used as an adjective phrase, it should be written with a hyphen to avoid ambiguity:

*Client-side processing handles the validation.*

### <a id="clientserver"></a>"client / server"

Use non-breaking spaces before and after the slash ("/") character. In AsciiDoc, this would be written as `client&nbsp;/&nbsp;server`.

### <a id="cloud"></a>"cloud"

### <a id="codebase"></a>"codebase"

The spelling is *codebase*; not *code base*.

### <a id="colon"></a>colon (“:”)

The function of a colon in a sentence is to signal the beginning of an explanation or a list.\
Often, we can think of it as saying\
*and this is it…*\
or\
*and the following is what I’m talking about…*.\
Some examples of this are:

*There can be only one reason he is late**:** he has missed the flight.*\
*Annabel has three valuable characteristics**:** she is clever, she is conscientious, and she is honest.*\
*On seeing the results of my work, I felt only one emotion**:** pride.*

A colon is also commonly used to introduce a list, particularly at the end of a sentence.\
For example:

*The parameter can be of several types**:** integer, boolean, or string.*\
*Three cities are in the running to stage the next Olympics**:** Beijing, Chicago, and Melbourne.*

A colon shouldn’t be used to join two full clauses outside the uses mentioned here.\
If you are looking for the right punctuation to join two clauses that have some logical relationship, consider using a [semi-colon](https://vaadin.com/docs/v23/contributing-docs/style-guide/grammar.md#grammar.semi-colon).\
Don’t use a comma for this purpose. (See [comma splice](https://vaadin.com/docs/v23/contributing-docs/style-guide/grammar.md#grammar.comma_splice).)

Vaadin uses US English in its documentation. US usage allows a colon to be followed by a sentence beginning with a capital letter, if that sentence is the first of two or more sentences that are governed by the same colon.

<!-- vale Vaadin.JustSimply = NO -->

*There may be several reasons to learn Esperanto**: I**t is completely regular, so you don’t need to learn a lot of exceptions. It isn’t associated with any specific country, so has no political baggage. Finally, it’s just fun to learn.*

<!-- vale Vaadin.JustSimply = YES -->

However, if the colon governs only one sentence, begin the sentence with a lowercase letter:

*I can give you one good reason to learn Esperanto**: i**t is fun to learn.*

### <a id="word-list.color_blind"></a>"color-blind"

Use the term *color-blind* only in its literal sense, to refer to a person who is unable to distinguish certain colors.

### <a id="combo-box"></a>"combo box"

<!-- vale Vale.Spelling = NO -->

Not *combobox*.

<!-- vale Vale.Spelling = YES -->

### <a id="command-line"></a>"command line"

When it’s used as a noun phrase, write *command line*. When it’s used as an adjective phrase, write *command-line*. For example:

*You can invoke the tool from the command line.*\
\[Noun phrase]

*Several command-line options are available.*\
\[Adjective phrase]

However, see ["command line interface"](#word-list.command_line_interface)

### <a id="word-list.command_line_interface"></a>"command line interface"

This is a common, easily recognized phrase, so it’s unnecessary to hyphenate *command line* here.

In the first reference in the document, write this as *command line interface ("CLI")*. In subsequent occurrences, it’s acceptable to write it as *CLI*.

### <a id="command-prompt"></a>"command prompt"

In the context of the command line interface, the *command prompt* indicates the location where the user may enter a command. Typical command prompts are "$ " (in Unix-like systems) and "C:\\> " (in Windows-based systems).

### <a id="consist-of"></a>"consist of"

This indicates that one thing is made up of one or more other things, and nothing else. If you want to say that one thing is made up of one or more things **plus** some other things, use *include*. For example:

*The course consists of six modules.*\
\[In other words, there are six (and only six) modules in the course.]

*The course includes two modules on object-oriented design.*\
\[In this case, the two modules on object-oriented design are a part of the course.]

<!-- vale Vale.Spelling = NO -->

### <a id="config"></a>"config"

<!-- vale Vale.Spelling = YES -->

Avoid this as an abbreviation for *configuration*. Spell it out in full.

### <a id="cpu"></a>"CPU"

### <a id="css"></a>"CSS"

It’s acceptable to use *CSS*, rather than write out *cascading style sheets* in full.\
Don’t use the extension *.css* to refer to a file type.

### <a id="cross-site-request-forgery"></a>"cross-site request forgery"

On the first mention, write this as *cross-site request forgery (CSRF)*. On subsequent mentions, *CSRF* is sufficient.

### <a id="csv"></a>"CSV"

Don’t use the extension *.csv* to refer to a file type.\
Instead, use the capitalized abbreviation *CSV*.\
For example:

*You can download this as a **CSV** file.*\
\[Not *a .csv file*.]

## <a id="d"></a>D

### <a id="data"></a>“data”

Although *data* is, strictly speaking, a plural Latin form, the generally accepted convention is to treat it as singular. For example:

*We need to ensure that the data is encrypted.*\
\[Not *the data are encrypted*]

### <a id="daylight-saving-time"></a>"daylight saving time"

### <a id="decrement"></a>"decrement"

The verb *decrement* means to decrease an integer by a specified value. It’s the opposite of *increment*.

### <a id="definite-article-the"></a>definite article (“the”)

### <a id="deprecate"></a>"deprecate"

In the context of software development, if something is *deprecated*, it means that it’s **recommended** not to use this thing.\
It doesn’t mean that it isn’t possible to use it.

The term *deprecated* is often used in situations where that particular thing is scheduled to become unavailable at some point in the future.

### <a id="desire"></a>"desire"

Don’t use *desire* as a synonym for *want*.\
Instead, use *want*.

### <a id="determinate-progress-bar"></a>"determinate progress bar"

A *determinate progress bar* is a progress indicator that informs the user how much of a process has been completed, and how much remains to be done.

### <a id="devops"></a>"DevOps"

An abbreviation of *development operations*. Write it as *DevOps*.

### <a id="dialog"></a>"dialog"

<!-- vale Vaadin.EN_US = NO -->

A *dialog* or *dialog box* is an element of the user interface.\
A *dialogue* is a conversation between two people.

<!-- vale Vaadin.EN_US = YES -->

### <a id="different"></a>"different"

Use *different from*, rather than *different than* or *different to*.

### <a id="direction-keys"></a>"direction keys"

Don’t use the term *direction keys*.\
Instead, use *arrow keys*.

### <a id="directory"></a>"directory"

Use *directory*, instead of *folder*, unless there is a good reason to do otherwise.\
One such reason might be that the tool under discussion uses the term *folder* in its user interface.

### <a id="distributed-denial-of-service"></a>"distributed denial-of-service"

On the first mention, write *distributed denial-of-service (DDOS)*. On subsequent mentions, it’s sufficient to write *DDOS*.

### <a id="dns"></a>"DNS"

*DNS* is an abbreviation of *Domain Name System* (not *Server*), which is a protocol.\
A server that operates this system is a *DNS server*.\
A client of such a server is a *DNS client*.

### <a id="document"></a>"document"

Write this in full.\
Don’t write *doc*.

### <a id="domain-name-registrar"></a>"domain name registrar"

### <a id="dos-and-donts"></a>"dos and don’ts"

### <a id="dropdown"></a>“dropdown”

Use *overlay* rather than *dropdown*.

### <a id="due-to"></a>"due to"

Avoid using *due to*.\
Instead, use *because of* or *as a result of*.

## <a id="e"></a>E

### <a id="e-book"></a>"e-book"

### <a id="e-commerce"></a>"e-commerce"

<!-- vale Google.Latin = NO -->

<!-- vale Microsoft.Foreign = NO -->

### <a id="e-g"></a>"e.g."

Avoid using *e.g.*\
Instead, write *for example*.

<!-- vale Microsoft.Foreign = YES -->

<!-- vale Google.Latin = YES -->

### <a id="either"></a>“either”

Like the word *both*, the word *either* is used in the context of two things.\
For example:

*The parameter can be **either** an integer or a boolean.*

It isn’t correct to use *either* where there is a choice between more than two things.\
For example, this is incorrect:

*The parameter can be **either** an integer, a boolean or a string.*

In such a case, we could say, for example:

*The parameter can be an integer, a boolean, or a string.*

For added emphasis, we could also say:

*The parameter can be any of an integer, a boolean, or a string.*

For clarity, *either* should be placed as close as possible to the point where choice occurs.\
For example:

<!-- vale Vale.Spelling = NO -->

*You can choose **either** to ignore the message or to fix the problem before continuing.*\
\[This is OK, because the choice is either to ignore or to fix.]

*You can **either** choose to ignore the message or to fix the problem before continuing.*\
\[Inappropriate, because the choice isn’t whether to choose or not to choose.]

### <a id="element"></a>"element"

Use *element*, rather than *tag*, when referring to HTML elements.

### <a id="email"></a>"email"

### <a id="end-user"></a>"end user"

The noun is *end user*. The adjective phrase is *end-user*. For example:

*The choice of license depends on the number of **end users**.*\
*This minimizes the level of **end-user** support that you need to provide.*

### <a id="enter"></a>"enter"

In the context of IT systems, *to enter* refers to inputting a specific piece of data to the system. For example:

*Enter your user ID and press OK.*

### <a id="esc-key"></a>"Esc key"

### <a id="etc"></a>"etc."

This abbreviation is always terminated by a period.

Don’t use *etc.* in situations where it isn’t clear exactly what it means.\
For example:

*Always be sure to include the currency symbol, such as "$", "£", "€", **etc**.*\
\[Here, it’s clear that *etc.* refers to all the other possible currency symbols.]

*Check that the problem wasn’t caused by a misspelt variable name, **etc.***\
\[In this case, it’s unclear what other issues might have caused the problem.]

<!-- vale Vaadin.HeadingPunctuation = NO -->

## <a id="f"></a>F

### <a id="f1-f2-f3-etc"></a>"F1", "F2", "F3", etc.

<!-- vale Vaadin.HeadingPunctuation = YES -->

### <a id="faq"></a>"FAQ"

*FAQ* is an abbreviation for *frequently asked question*. The term is sufficiently well known for it not to need explanation.\
The plural is *FAQs*.

### <a id="fast-forward"></a>"fast-forward"

*Fast-forward* can be a noun, an adjective or a verb.

### <a id="fewer"></a>"fewer"

*Fewer* (not *less*) should be used with countable nouns. For example:

*There were **fewer** problems with this version of the software.*\
\[Not *less problems*.]

***Fewer and fewer** people use landlines these days.*\
\[Not *less and less people*.]

### <a id="fiber-optics"></a>"fiber optics"

### <a id="field"></a>"field"

Use the term *field* in the context of databases.\
Don’t use *field* in the context of the UI.\
Instead, use, for example, *box*.

### <a id="filename"></a>"filename"

### <a id="firewall"></a>"firewall"

### <a id="firmware"></a>"firmware"

### <a id="floating-point"></a>"floating-point"

*Floating-point* is an adjective.

### <a id="following"></a>"following"

*Following* may be used with some more specific term. For example:

*the **following** example*\
*the **following** text*\
*the **following** procedure*

However, it may not always be necessary to be so specific.\
We may use the expression *the following* as a noun phrase on its own.\
For example:

***The following** is an example of how to use this functionality.*\
*It may be instantiated using the default parameters, as in **the following**:*

### <a id="font-size"></a>"font size"

### <a id="for-example"></a>"for example"

Use *for example* in preference to *e.g.*

If you use *for example* in the middle of a sentence, use a semi-colon if there is a possibility of doubt which part of the sentence it relates to.\
For example:

*US and UK spelling have some differences, **for example**, the preference for* z *or* s *in verbs that end in -ize.*\
\[On first reading, the reader may hesitate over which part of the sentence *for example* refers to.]

*US and UK spelling have some differences; for example, the preference for* z *or* s *in verbs that end in* -ize.\
\[The semi-colon makes it easier for the reader to interpret the sentence correctly on first reading.]

### <a id="word-list.former"></a>“former”

The word *former* identifies the first of **two** options previously mentioned. (*Former* is often used in conjunction with *latter*, which indicates the **last** of two options previously mentioned.)\
It isn’t correct to use *former* in a situation where more than two options have been mentioned.\
For example:

*Anil spends his spare time playing squash and doing crosswords. The **former** helps him to stay fit; the **latter** keeps his brain sharp.*

*Former* is also used as an adjective to indicate that a person or place had a certain role in the past. For example:

*Anne is a **former** systems analyst who now acts as a security consultant to the company.*\
\[That is, Anne used to be a systems analyst.]

*The company has its offices in a **former** bakery.*\
\[That is, the company’s offices used to be a bakery.]

### <a id="forward-compatibility"></a>"forward compatibility"

The noun is *forward compatibility*.\
The adjective is *forward-compatible*.

### <a id="freeze"></a>"freeze"

Don’t use *freeze* to refer to a situation when a program stops responding.\
Instead, write *stops responding*.

### <a id="frontend"></a>“frontend”

The noun phrase is *frontend*.\
The adjective is *front-end*.\
For example:

*Processing takes place at the **frontend**.*\
***Front-end** processing is kept to a minimum.*

## <a id="g"></a>G

### <a id="gbps"></a>"Gbps"

Abbreviation of *gigabits per second*.\
Don’t use *Gb/s*.

### <a id="gdpr"></a>"GDPR"

On the first mention, use *the General Data Protection Regulation (GDPR)*.\
On subsequent mentions, use *the GDPR*.

### <a id="gif"></a>"GIF"

Don’t use the extension *.gif* to refer to a file type.

### <a id="gray"></a>"gray"

## <a id="h"></a>H

### <a id="half"></a>"half"

In compound phrases with *half*, use a hyphen. For example:

*half-life*\
*half-length*\
*half-price*

### <a id="handheld"></a>"handheld"

### <a id="hang"></a>"hang"

Don’t use *hang* to refer to a situation when a program stops responding.\
Instead, write *stops responding*.

### <a id="hard-disk"></a>"hard disk"

### <a id="hard-drive"></a>"hard drive"

### <a id="hard-code"></a>"hard-code"

The verb is *hard\_code*.\
The adjective is *hard-coded*.

### <a id="he-she-they"></a>“he” / “she” / “they”

It’s important to avoid using gender-specific pronouns (unless there is a significant reason for doing so).\
Don’t overuse *he / she* or *he or she*, as this quickly becomes tedious.

The generally accepted approach is to use the pronoun *they*.\
For example:

*Each person must do what **they** think best.*\
\[Not *what he or she thinks best*.]

However, if you can easily avoid the issue by using the plural, do so.\
For example:

***People** must do what **they** think best.*

### <a id="hexadecimal"></a>"hexadecimal"

Write out *hexadecimal* in full.\
Don’t abbreviate it to *hex*.

### <a id="hierarchy"></a>“hierarchy”

### <a id="his-her-their"></a>“his” / “her” / “their”

### <a id="hit"></a>"hit"

Don’t use *hit* to refer to pressing a key.\
Instead, use *press*.

### <a id="home-page"></a>"home page"

### <a id="hopefully"></a>“hopefully”

Don’t use *hopefully* to mean *it’s hoped that*.\
For example:

*Hopefully, the new version is released at the beginning of July.*

Instead, use *\<the subject of the sentence> hopes to*.\
If you must use a passive construction, write *it’s hoped that*.\
For example:

*The company hopes to release the new version at the beginning of July.*\
**or**\
*It’s hoped that the new version is released at the beginning of July.*

### <a id="host-name"></a>"host name"

### <a id="hyperlink"></a>"hyperlink"

Use *hyperlink* in preference to *link*.

## <a id="i"></a>I

<!-- vale Microsoft.Foreign = NO -->

<!-- vale Google.Latin = NO -->

### <a id="i-e"></a>"i.e."

Avoid using *i.e.*\
Instead, use *that is*.

### <a id="io"></a>"I/O"

It’s OK to write *I/O*, with no spaces.\
If you expand it to *input / output*, insert non-breaking spaces (`&nbsp;`) around the slash character.

### <a id="if-clauses-in-the-future"></a>“if” clauses in the future

Clauses that refer to conditions in the future use the present tense.\
The "result" clause uses the appropriate future form or imperative form.\
For example:

<!-- vale Vaadin.Will = NO -->

*If there **are** any further releases, you will receive an advisory email.*\
\[Not *If there will be….*]

*Send us a message via our contact page if you **have** any problems.*\
\[Not *If you will have….*]

<!-- vale Vaadin.Will = YES -->

See also [time clauses in the future](https://vaadin.com/docs/v23/contributing-docs/style-guide/grammar.md#grammar.time_clauses_in_future)

### <a id="if-or-whether"></a>"if" or "whether"

Use *if* in clauses that express a simple conditional meaning.\
Use *whether* in clauses that express uncertainty between two possibilities. Sometimes, either is acceptable.\
For example:

*Let me know **if** you need help.*\
\[This is a simple condition; that is, if the situation arises that you need help, let me know.]

*Let me know **whether** the fix works.*\
\[That is, let me know which of the situations is true: does the fix work, or doesn’t it work?]

### <a id="in-order-to"></a>“in order to”

Use *in order to* for clarity, especially after verbs that are followed by the infinitive (*to*) form, such as *need*, *want*, *start*.\
For example:

*This the information you **need to use** the components correctly.*\
\[The reader may misinterpret this on first reading.]

*This the information you **need in order to use** the components correctly.*\
\[Slightly more verbose, but clearer.]

### <a id="indent"></a>"indent"

*Indent* is a verb that means to apply a greater left (and sometimes right) margin to text than that of the preceding material.\
The purpose of indentation is to show some distinction between one piece of text and the next.

Don’t use *outdent*, as it’s often unclear what exactly this means in a given situation. Look for a different way to express this idea.

### <a id="indeterminate-progress-bar"></a>"indeterminate progress bar"

An *indeterminate progress bar* is a progress indicator in a situation where it isn’t possible to determine and show how much of the process remains to run.

### <a id="information"></a>“information”

"Information" is an [uncountable](https://vaadin.com/docs/v23/contributing-docs/style-guide/grammar.md#grammar.countable_entities) noun. In other words, we can’t talk about *one information*, *two informations*, etc.\
For the same reason, we can’t say *an information*, as this implies a quantity of one.

If we want to talk about quantity in relation to information, there are several options:

- use an intermediary word, such as *piece* or *bit*

- use a quantifier, such as *a lot of*, *lots of*, *some*, *a little*, etc.

### <a id="input"></a>"input"

Don’t use *input* as a verb.\
Instead, write *enter*.

### <a id="internet"></a>"internet"

### <a id="internet-of-things"></a>"Internet of Things"

On the first mention, write as *Internet of Things (IoT)*.\
On subsequent mentions, write as *IoT*.

### <a id="insertion-point"></a>"insertion point"

The point on the screen where the user enters data.

### <a id="italics"></a>"italics"

The noun is *italics*.\
The adjective is *italic*.\
The verb is *italicize*.

### <a id="its-or-its"></a>“its” or “it’s”

The possessive form of *it* is *its*, with no apostrophe.\
This is logical and consistent with the other possessive adjectives:\
*I* → *my*\
*you* → *your*\
*he* → *his*\
*she* → *her*\
*they* → *their*\
etc.\
Possessive adjectives have no apostrophes.

*It’s* (with the apostrophe) is a contracted form, similar to *I’m*, *you’re*, *he’s*, etc.\
Here, the apostrophe performs its classical role of indicating that letters have been omitted.\
*It’s* can mean *it is* or *it has*; the context always tells us which meaning is intended.

***It’s** easy to make a mistake.*\
\[*It’s* must mean *it is*, since *It has easy…* makes no sense at all.]

***It’s** been a difficult day.*\
\[*It’s* must mean *it has*, since *It’s been…* makes equally little sense.]

## <a id="j"></a>J

### <a id="javascript"></a>"JavaScript"

### <a id="jpeg"></a>"JPEG"

Don’t use the filename extension *.jpg* to refer to a file type.

### <a id="justified"></a>"justified"

Text that is *justified* is aligned on the left and on the right.

## <a id="k"></a>K

### <a id="kbps"></a>"Kbps"

Abbreviation for *kilobits per second*.\
Don’t use *kb/s*.

### <a id="key"></a>"key"

Don’t use this as a synonym for "crucial".

### <a id="key-value-pair"></a>"key-value pair"

Use a hyphen, rather than an en-dash.

### <a id="keypress"></a>"keypress"

### <a id="keystroke"></a>"keystroke"

### <a id="keyword"></a>"keyword"

### <a id="knowledge-base"></a>"knowledge base"

## <a id="l"></a>L

### <a id="l-or-ll"></a>“-l-” or “-ll-”?

In US English (which is used in Vaadin documentation), if a verb ends in the letter *l*, the final *l* isn’t usually doubled when a suffix (*-ing*, *-ed*, *-er*) is added.\
The exception is when the final syllable is stressed.\
For example:

*cancel*, *canceling*, *canceled*\
*travel*, *traveling*, *traveled*\
*excel*, *excelling*, *excelled*

### <a id="labeled"></a>"labeled"

### <a id="latter"></a>“latter”

See ["former"](#word-list.former)

### <a id="layout-lay-out"></a>"layout", "lay out"

The noun is *layout*.\
The verb is *lay out*.

### <a id="lead"></a>"lead"

The past simple and past participle of *lead* is *led*. For example:

*This situation led to various problems.*\
*He has led the company since 2006.*

### <a id="leverage"></a>"leverage"

Avoid using this as a verb.\
Consider using *take advantage of* or *make effective use of*.

### <a id="like-or-as"></a>“like” or “as”?

See ["as" or "like"?](#word-list.as_or_like)

### <a id="list-box"></a>"list box"

### <a id="livestream"></a>"livestream"

### <a id="login"></a>"login"

The noun is *login*.\
The verb is *to log in (to)*.

### <a id="lower"></a>"lower"

Don’t use *lower* to refer to earlier versions of software.\
Instead, use *earlier*.

## <a id="m"></a>M

### <a id="macos"></a>"macOS"

Use *macOS*, even at the beginning of a sentence.

### <a id="mailbox"></a>"mailbox"

### <a id="markup"></a>"markup"

The noun is *markup*.\
The verb is *to mark up*.

### <a id="masterslave"></a>"master / slave"

Avoid this term.\
Instead, consider using *primary / subordinate*.

### <a id="matrix"></a>"matrix"

The plural is *matrices*.

### <a id="mbps"></a>"Mbps"

Abbreviation of *megabits per second*.\
Not *Mb/s*.

### <a id="metadata"></a>"metadata"

### <a id="method"></a>"method"

As our documentation deals extensively with Java objects and methods, avoid using *method* to mean *way* or *process*.

### <a id="mime"></a>"MIME"

It’s usually unnecessary to write out this term in full.\
However, if it’s required for some reason, it’s *multipurpose internet mail extensions*.

### <a id="mobile"></a>"mobile"

Use *mobile*, *mobile phone*, or *mobile device*.\
Don’t use *cell phone*.

### <a id="movable"></a>"movable"

Don’t use *moveable*.

### <a id="much"></a>"much"

*Much* is frequently used in questions and negative statements, but not usually in positive statements.\
In positive statements, use an alternative expression, such as *a lot of*, *a great deal of*, or *a large amount of*.\
For example:

*Is there **much** difference between version 1 and version 2?*\
*No, there is **not much** difference between version 1 and version 2.*\
*Yes, there is **much** difference between version 1 and version 2.*\
*Yes, there is **a lot of** difference between version 1 and version 2.*

### <a id="multifactor-authentication"></a>"multifactor authentication"

## <a id="n"></a>N

### <a id="na"></a>"N/A"

Use this abbreviation of *not applicable* in tables or other contexts where space is limited.

### <a id="name-server"></a>"name server"

### <a id="namespace"></a>"namespace"

### <a id="nat"></a>"NAT"

Abbreviation of *network address translation*.

### <a id="needed"></a>"needed"

Don’t use *needed* attributively (that is, before the noun phrase that it describes). Instead, use *required*. For example:

*Edit the code and make the **required** changes.*

*Edit the code and make the **needed** changes.*\
\[Don’t use *needed* attributively.]

*Edit the code and make the changes that are **needed**.*\
\[It’s OK to use *needed* predicatively.]

### <a id="network"></a>"network"

Write *network* out in full.\
Don’t shorten it to *net*.

### <a id="nosql"></a>"NoSQL"

### <a id="npm"></a>“npm”

### <a id="null"></a>"null"

In general contexts, use the term *null* to refer to a null value.

## <a id="o"></a>O

### <a id="oauth-2-0"></a>"OAuth 2.0"

### <a id="of"></a>"of"

Don’t add *of* to prepositions where it isn’t necessary. For example:

*inside of the parentheses*\
\[Instead, write *inside the parentheses*.]

*off of the premises*\
\[Instead, write *off the premises*.]

### <a id="ok"></a>"OK"

Write *OK*, not *okay*.

### <a id="on-premises"></a>"on-premises"

Write *on-premises* in full, not *on-prem*.

### <a id="once"></a>"once"

Don’t use *once* to mean *after*, as it can be confusing.\
Use *after* or *when*.\
For example:

*Once you have created the object, you need to initialize it.*

Instead, write\
*When you have created…*\
or\
*After you have created…*

### <a id="open-source"></a>"open source"

As this is a common phrase, it’s unnecessary to use a hyphen, even when it’s used as an adjective phrase.

### <a id="os"></a>"OS"

Is it unnecessary to write out this abbreviation of *operating system* in full.

### <a id="over"></a>"over"

Don’t use *over* in the sense of *more than*. Instead, use *more than*.

### <a id="overlay"></a>“overlay”

## <a id="p"></a>P

### <a id="parent-child"></a>"parent-child"

### <a id="pdf"></a>"PDF"

Don’t use the extension *.pdf* to refer to a file type.

### <a id="per"></a>"per"

Use *per* instead of the slash character ("/") to refer to a rate. For example:

*bits per second*\
\[Not *bits/second*.]

*words per minute*\
\[Not *words/minute*.]

### <a id="persist"></a>"persist"

The verb *persist* doesn’t take an object (that is, it’s intransitive).\
For example:

*We want the user ID to **persist** between sessions.*\
\[That is, the user ID should be retained.]

We want to **persist the user ID** between sessions.\
\[The verb *persist* doesn’t take an object.]

<!-- vale Vaadin.Please = NO -->

### <a id="please"></a>"please"

Don’t use *please* in the context of instructions.\
It’s unnecessary.

<!-- vale Vaadin.Please = YES -->

### <a id="plugin"></a>"plugin"

### <a id="png"></a>"PNG"

Don’t use the file extension *.png* to refer to a file type.

### <a id="post"></a>"post"

Don’t use *post* as a synonym for *after*.\
Instead, use *after*.

### <a id="postal-code"></a>"postal code"

Use *postal code* rather than *postcode* or *zip code*.

### <a id="practice"></a>“practice”

In US English, *practice* is a noun and a verb.

### <a id="precondition"></a>"precondition"

### <a id="press"></a>"press"

Use the verb *press* to refer to pressing a key or key combination.\
Don’t use *hit* in this context.

## <a id="q"></a>Q

## <a id="r"></a>R

### <a id="real-time"></a>"real time"

The noun phrase is *real time*.\
The adjective phrase is *real-time*.\
For example:

*The data is retrieved in real time.*\
*Real-time processing takes place at the frontend.*

### <a id="regular-expression"></a>"regular expression"

Don’t use *regex*.

### <a id="repository"></a>“repository”

Don’t use *repo*.

### <a id="respectively"></a>“respectively”

The adverb *respectively* is used in a well-defined grammatical context.\
It has the function of distributing meaning over a defined set of entities.\
For example:

*The research department, marketing department, and customer services department are located in San Francisco, New York, and New Orleans **respectively**.*

Don’t use *respectively* in any other construction.

### <a id="rest"></a>"REST"

It’s unnecessary to write out this abbreviation of *representational state transfer* in full.

### <a id="runtime"></a>"runtime"

## <a id="s"></a>S

### <a id="s-es"></a>"(s)", "(es)"

Don’t append *(s)* or *(es)* to a singular word in order to indicate that the item in question may or may not be plural.\
For example:

*Select the **file(s)** that you wish to upload.*

Instead, either use the plural word only, or explicitly give both forms.\
For example:

*Select the **files** that you wish to upload.*\
or\
*Select the **file or files** that you wish to upload.*\
\[It’s usually unnecessary to be so explicit.]

### <a id="word-list.s_or_z"></a>“-ise” or “-ize”

In US English, the suffix *-ize* is generally preferred over *-ise*.

### <a id="separator"></a>“separator”

Use *divider* rather than *separator*.

### <a id="server-side"></a>“server side”

### <a id="service-level-agreement"></a>"service level agreement"

On the first mention, write it as *service level agreement (SLA)*.\
On subsequent mentions, write it as *SLA*.

### <a id="setup"></a>"setup"

The noun and adjective are *setup*.\
The verb is *to set up*.

### <a id="sha-1"></a>"SHA-1"

### <a id="ship"></a>"ship"

Don’t use *ship* to refer to software releases.\
Instead, use *release*.

### <a id="sign-in"></a>"sign-in"

The noun and adjective are *sign-in*.\
The verb is *to sign in (to)* (not *to sign into*).

### <a id="smartphone"></a>"smartphone"

Don’t use the term *smartphone*.\
Instead, use *mobile* or *mobile phone*.

### <a id="software-as-a-service"></a>“software as a service”

At the first mention, write *software as a service (SaaS)*.\
On subsequent mentions, write *SaaS*.

### <a id="space-key"></a>"space key"

### <a id="specification"></a>"specification"

Write *specification* out in full.\
Don’t abbreviate it to *spec*.

### <a id="ssh-ssh"></a>"ssh", "SSH"

*ssh* is the terminal utility.\
*SSH* is the associated communications protocol.

### <a id="startup"></a>"startup"

The noun and adjective are *startup*.\
The verb is *to start up*.

### <a id="status-bar"></a>"status bar"

### <a id="style-sheet"></a>"style sheet"

### <a id="subclass"></a>"subclass"

*Subclass* is a noun and a verb.

### <a id="subcomponent"></a>"subcomponent"

### <a id="subnet"></a>"subnet"

### <a id="sync"></a>"sync"

The verb forms are *sync*, *syncing*, *synced*.

## <a id="t"></a>T

### <a id="tar"></a>"tar"

Don’t use the extension *.tar* to refer to a file type.\
For example:

*a **tar** file*

### <a id="that"></a>“that”

If the word *that* is optional, include it for clarity.\
The goal, as always, is to help the reader to interpret each phrase and sentence correctly at the first reading.\
For example:

*… to **guarantee your software** works correctly*,

*… to guarantee **that** your software works correctly*.

### <a id="word-list.that_or_which"></a>“that” or “which”?

In defining relative clauses (see [relative clauses](https://vaadin.com/docs/v23/contributing-docs/style-guide/grammar.md#grammar.relative_clauses)), we can use either *that* or *which*.\
For example:

*The company **that** developed the software provides excellent support.*\
or\
*The company **which** developed the software provides excellent support.*

However, in non-defining relative clauses (see [relative clauses](https://vaadin.com/docs/v23/contributing-docs/style-guide/grammar.md#grammar.relative_clauses)), we can’t use *that*.\
For example:

*I emailed technical support at BrilSoft, which developed the software.*\
\[Not *… at BrilSoft, that developed the software*.]

<!-- vale Vaadin.Contractions = NO -->

### <a id="their-or-theyre"></a>“their” or “they’re”?

Because the pronunciation of *their* and *they’re* is identical, it’s easy to write the wrong form.\
This error is less likely to happen in our technical documentation, as we have made the decision not to use contracted forms.\
In general, the form *they’re* shouldn’t be used in our technical documentation.

<!-- vale Vaadin.Contractions = YES -->

### <a id="time-frame"></a>“time frame”

Use *time frame* rather than *timeframe*.

### <a id="time-out"></a>"time out"

The verb is *time out*.\
The noun and adjective are *time-out*.

### <a id="time-stamp"></a>"time stamp"

The noun is *time stamp*.\
The adjective and verb are *time-stamp*.

### <a id="time-zone"></a>"time zone"

If a time zone has an unambiguous name, write it out in full, capitalized on the first use.\
Use *Coordinated Universal Time (UTC)* rather than *Greenwich Mean Time (GMT)*.\
For example:

*The first backup was set to run at 09∶00 **Coordinated Universal Time (UTC)**.*\
*The second backup was set to run at 23∶00 **UTC**.*

If the time zone doesn’t have a name, or to guard against misunderstanding, use the form *UTC-n* or *UTC+n*.\
For example:

*The videoconference is scheduled for 14∶30 **UTC-7**.*\
*The system went down at 21∶43 **UTC+9**.*

### <a id="toolkit"></a>"toolkit"

### <a id="touchscreen"></a>"touchscreen"

### <a id="trailing"></a>"trailing"

Use *trailing* to refer to characters that occur at the end of a string.\
The opposite of *trailing* is *leading*.

### <a id="trojan"></a>"trojan"

Use *trojan* or *trojan horse*.

## <a id="u"></a>U

### <a id="united-kingdom"></a>"United Kingdom"

Use *the United Kingdom* or *the UK* to refer to the sovereign state.\
Don’t use *Great Britain*, *Britain*, or *England* in this sense.

### <a id="unique"></a>“unique”

Something is either unique or it isn’t. There can be no degrees of uniqueness.\
Hence, avoid using such expressions as *very unique* or *rather unique*.

### <a id="unzip"></a>"unzip"

Don’t use *unzip*.\
Instead, use *extract*.

### <a id="uppercase"></a>"uppercase"

### <a id="url"></a>"URL"

The plural is *URLs*.

### <a id="us"></a>"US"

Don’t use *U.S.*

### <a id="username"></a>"username"

### <a id="utf"></a>"UTF"

*UTF-8*, *UTF-16*, *UTF-32*.

### <a id="utilize"></a>"utilize"

Avoid *utilize*.\
Instead, use *use*.

## <a id="v"></a>V

### <a id="v-2"></a>"v."

Use *v.* as the abbreviation for *version*.\
For example:

Atom v. 1.57.0

However, the exception is Vaadin’s own software, since historically a capital *V* is used in this context.\
For example:

*Vaadin 21*\
*This was introduced in **V 20**.*

### <a id="via"></a>"via"

Avoid using *via*.

### <a id="vice-versa"></a>"vice versa"

Avoid using *vice versa*, as it’s often unclear exactly what is meant.\
Use more-specific language.

### <a id="videoconference"></a>"videoconference"

### <a id="voicemail"></a>"voicemail"

### <a id="vs"></a>"vs"

Write *versus* in full, or abbreviate it to *vs* without a final period.\
Avoid using *versus* in the sense of *compared with* or *as opposed to*.

## <a id="w"></a>W

### <a id="w3c"></a>"W3C"

### <a id="was-or-were"></a>"was" or "were"?

In English, the subjunctive mood has largely fallen out of use.\
However, it still exists in certain set constructions.\
For example:

*If I **were** you…*\
\[Not *If I was you…*.]

In other constructions, using a subjunctive form is generally optional.\
For example:

*If he **were** here, he could explain it to you.*\
*If he **was** here, he could explain it to you.*\
\[Both of these are acceptable.]

*It’s necessary that you **be** here.*\
*It’s necessary that you **are** here.*\
\[Both of these are acceptable.]

*It’s important that she **have** experience.*\
*It’s important that she **has** experience.*\
\[Both of these are acceptable.]

In some cases, you can avoid the issue by using alternative forms.\
For example:

*It’s necessary **for you to be** here.*\
*It’s important that she **should have** experience.*

### <a id="web"></a>"web"

Use *web* when referring to the World Wide Web.

### <a id="web-based"></a>"web-based"

### <a id="webpage"></a>"webpage"

### <a id="website"></a>"website"

### <a id="well-being"></a>"well-being"

### <a id="which-or-that"></a>“which” or “that”?

See ["that" or "which"?](#word-list.that_or_which)

### <a id="while"></a>"while"

Use *while* in expressions of time.\
Don’t use *while* as a synonym for *although* or *whereas*.\
For example:

***While** it’s possible to write code using an ordinary text editor, using an IDE has significant advantages.*\
***Although** it’s possible to write code using an ordinary text editor, using an IDE has significant advantages.*

*The previous version was written in C++, **while** the current version is Java-based.*\
*The previous version was written in C++, **whereas** the current version is Java-based.*

### <a id="white-paper"></a>"white paper"

### <a id="who-or-that"></a>"who" or "that"?

Use *who*, rather than *that*, in relative clauses that refer to people. For example:

*Users **who** require training.* \[Not *Users that require training*.]

### <a id="whom"></a>"whom"

In general, try to avoid using *whom*. It can sound pretentious.

However, it’s sometimes difficult to avoid elegantly.\
For example:

***To whom** were you talking?*\
\[This is grammatically correct, but it sounds pretentious.]

***Who** were you talking to?*\
\[This sounds much more natural.]

Sometimes it’s preferable to use *whom* to avoid an awkward sentence.\
For example:

*This is the customer **for whom** we selected the appropriate product, rewrote the core module, and delivered training to the sales and marketing staff.*

*This is the customer **who** we selected the appropriate product, rewrote the core module, and delivered training to the sales and marketing staff **for**.\
\[Here, the preposition \_for* is so far from its associated relative pronoun (*who*) that the reader is likely to lose track of the meaning.]

### <a id="whose-or-whos"></a>“whose” or “who’s”?

Although these two words sound exactly the same, they have completely different meanings.

*Whose* means *of whom* or *of which*.\
For example:

*This is the user **whose** account was blocked.*\
\[That is, the user *of whom* the account was blocked.]

*This is the server **whose** hard disk failed.*

*Who's* is a contraction of *who is* or *who has*.

### <a id="wi-fi"></a>"Wi-Fi"

### <a id="wildcard"></a>"wildcard"

<!-- vale Vaadin.Will = NO -->

### <a id="will"></a>"will"

Try to avoid using the future form *will* unless you really are talking about the future.\
A common case is when talking about the behavior of software.\
For example:

*Press OK. A new dialog will open.*

*If there is no authenticated user, the method will return null.*

<!-- vale Vaadin.Will = YES -->

Instead, write

*Press OK. A new dialog opens.*

*If there is no authenticated user, the method returns null.*

### <a id="wireframe"></a>"wireframe"

### <a id="workspace"></a>"workspace"

### <a id="workstation"></a>"workstation"

## <a id="x"></a>X

### <a id="x-axis"></a>"x-axis"

### <a id="x-coordinate"></a>"x-coordinate"

## <a id="y"></a>Y

### <a id="y-axis"></a>"y-axis"

### <a id="y-coordinate"></a>"y-coordinate"

### <a id="yaml"></a>"YAML"

Don’t use the extension *.yaml* to refer to a file type.

## <a id="z"></a>Z

### <a id="z-axis"></a>"z-axis"

### <a id="z-coordinate"></a>"z-coordinate"

### <a id="zero"></a>"zero"

The plural of *zero* is *zeros*.

### <a id="zip"></a>"zip"

Don’t use the extension *.zip* to refer to a file type.

`ECF2A383-1FCE-4659-9697-480EA3A257AF`
