# Voice and Tone

Entries about verb usage, tense, voice (active vs passive), addressing the user, contractions, and tone choices from the Apple Style Guide.

## Entries

### abort
Avoid in user materials. See also [exit](#exit); [interrupt](#interrupt); [quit](#quit); [stop](#stop).

### access (n., v.)
It's OK to use *access* as a verb when you can't be more specific. Even in developer materials, consider more precise terms, such as *log in to*.

> Avoid: Access the server using an administrator account.
> Preferable: Log in to the server using an administrator account.
> Avoid: You can access the internet with your MacBook Air.
> Preferable: You can connect to the internet with your MacBook Air.

### activate, deactivate
Avoid; instead, use *turn on, turn off*.

### active
Use to refer to the app or window currently being used. Preferred to *in front*. See also [front, frontmost](#front-frontmost); [in front](#in-front).

### allow
Avoid using *allow* when you can restructure a sentence to make the reader the subject.

> Avoid: FileMaker Pro allows you to create a database.
> Preferable: You can create a database with FileMaker Pro.

See also [enable (v.), enabled (adj.)](#enable-v-enabled-adj); [let](#let).

### appear
Use *appear*, not *display*, to refer to items becoming visible on the screen.

> Correct: The setup assistant appears.
> Incorrect: The setup assistant is displayed.
> Incorrect: The setup assistant displays.

In a task, avoid stating that an item *appears*; if necessary for clarity, try to work it into the context of the task.

> 1. Click the close button.
> 2. In the message that appears, click Save.

However, it's OK to use *appear* in a task for information like the following:

> The printer icon appears only when there are jobs in the printing queue.
> Photos, videos, and any other files appear in a grid.

### assure
Don't use when you mean *ensure*. *Assure* means to state positively, so as to remove doubt.

> Assure customers that you'll resolve the issue.

See also [ensure, insure](word-choice-and-confusables.md#ensure-insure).

### attach
Don't use to mean *connect* (as in *Connect the USB device to your computer*).

### authenticate, authorize
Apple devices and services *authenticate* users to confirm their identity.

> Signing in with AppleConnect authenticates your identity and gives you access to Apple's internal apps and services.

Users *authorize* payments using methods such as a passcode. Users also *authorize* or *deauthorize* computers and devices. Banks and merchants *authorize* transactions when they confirm that the customer has the funds to pay for a purchase.

> To prevent unauthorized purchases, use Screen Time settings.
> To play some iTunes Store purchases, you must authorize your computer.

See also [code, passcode](word-choice-and-confusables.md#code-passcode).

### can, might, may
Use *can* to express the capacity to do something; use *might* or *may* to suggest the possibility of doing something; use *may* to express permission.

> You can log in to your account from another computer.
> You might be able to connect to the internet at a nearby hotspot.
> You may borrow my iPad if you return it tomorrow.

When used to express possibility, *might* typically suggests lower probability than *may*.

> If the issue persists, you may need to restart your computer or you might need to restore software.

### capability
If possible, avoid *capability* when you discuss features of software or hardware. Reword in terms of what the user can do with the feature.

> Correct: With Photos, you can create slideshows.
> Incorrect: Photos has the capability to create slideshows.

### choose
Use *choose*, not *select*, for menu items. In general, the user *selects* something (such as a file or disk icon, an email message, or a section of text) and then *chooses* a command to act on the selection.

> Choose View > Sort By > Date.
> Select the text to copy, and then choose Edit > Copy.
> Click the pop-up menu, and then choose High Priority.
> Control-click the TextEdit icon, and then choose Make Alias.

See also [menus](ui-elements.md#menus); [select (v.)](#select-v).

### click
Use to describe the act of selecting something or initiating an action by positioning the pointer over an onscreen element and briefly pressing and releasing the mouse or trackpad.

> To open Mail, click the Mail icon in the Dock.
> Click a disk icon to select it, and then choose File > Make Alias.

Don't use *click on*. Don't say *click the mouse* or *click the trackpad*; instead, use *press and release*.

> Press the mouse, drag to enclose the area you want to select, and then release.

See also [click and hold](#click-and-hold); [click in](#click-in); *double click (n.), double-click (v.), double-clicking (n., v.)*; [press](#press); [select (v.)](#select-v); [tap (n., v.)](#tap-n-v); *triple click (n.), triple-click (v.), triple-clicking (n., v.)*.

### click and drag
Don't use. You either *click* or *drag*.

> Correct: Drag the icon to the Trash.
> Incorrect: Click and drag the icon to the Trash.

### click and hold
Refers to the act of positioning the pointer on an item on the screen and pressing the mouse or trackpad until something happens.

> Click the Previous or Next button to go to the previous or next clip, or click and hold the Previous or Next button to rewind or fast-forward.

Don't use *click and hold* to refer to the act of pressing deeper on a Force Touch trackpad; use *force click*.

See also [click](#click); [force click (v.)](#force-click-v); [hold down](#hold-down); [press](#press); [touch and hold](#touch-and-hold).

### click in
You *click in* a window or other area of the screen, such as an image; you *click* other onscreen elements, such as icons and buttons. See also [click](#click).

### click on
Don't use; use *click*. See also [click](#click).

### close
In macOS, users *close* windows or documents and *quit* apps.

In iOS, users can *close* an app (stop using it temporarily) by pressing the Home button; doing so may not *quit* the app (stop the app from running altogether). You can also use *leave* to refer to closing an app.

> To leave an app and return to the Home Screen, press the Home button.

See also [open](#open); [quit](#quit).

### connect
Use to refer to the act of joining devices together; don't use *attach*, *hook up*, or *mate*. You *connect* USB devices to a computer, and you can *connect* computers to a network. Don't use *connect* when you mean *plug in*. See also [plug in (v.), plug into (v.)](word-choice-and-confusables.md#plug-in-v-plug-into-v).

### contractions
As part of Apple's informal voice, contractions are used and recommended throughout most documentation, interface text, and marketing copy. Keep localization in mind when deciding how or whether to use contractions.

- Use common contractions of be-verbs and auxiliary verbs with *not* (*aren't, isn't, can't, couldn't, didn't, doesn't, hadn't, haven't, weren't, won't*).

> You don't have access to the information.
> The error shouldn't occur again.

- Use common contractions of be-verbs and auxiliary verbs with personal pronouns (*he's, I'm, I've, it's, she'll, they're, we've, you're*). It's also OK to use *here's, let's, that's, there's,* and *what's*.

> Here's a quick look at what's new in this release.
> We're building a solar farm in China.

- Don't form contractions from nouns or proper nouns.

> Avoid: The computer's not working.
> Preferable: The computer isn't working.
> Avoid: Apple's going to introduce a new computer today.
> Preferable: Apple is going to introduce a new computer today.

- Avoid contractions of multipart verbs (*could've*), colloquialisms (*workin'*), and other contractions that are uncommon or awkward-sounding in written materials, or that may confuse nonnative English speakers (*everybody'd, how're, it'll, many's, when's, where'll, who've, why's*). Possible exceptions include text that's meant to be spoken (such as a script) and direct quotes in running text.

- Don't confuse *it's* (the contraction for *it is*) with *its* (a possessive pronoun).

> It's important for the department to keep track of its computers.

See also [possessives](punctuation.md#possessives).

### corrupted
Avoid if possible. Use *damaged* instead.

### crash
Don't use; use *quits unexpectedly*, *doesn't respond*, or *stops responding*. If you must use this word, put it in quotation marks and reassure the reader that the term *crash* doesn't imply damage to hardware or software.

### depress
Don't use; use *press*.

### desire
Don't use. See also [want](#want).

### desired
Try to avoid.

> Correct: make your changes, select the folder
> Incorrect: make the desired changes, select the desired folder

### disable (v.), disabled (adj.)
Don't use *disable* to refer to turning off a feature or deselecting an option; use *turn off* or *deselect*.

> You can turn off Airplane Mode using Control Center.
> To hide an object's caption, deselect the Caption checkbox.

Don't use *disabled* to describe features that are turned off or unavailable; use *turned off*, *unavailable*, or *inactive*.

> Make sure virus-protection software is turned off.
> The Copy command is unavailable if there's no text selected.
> Active roles appear in color in the timeline; inactive roles appear in gray.

See also [enable (v.), enabled (adj.)](#enable-v-enabled-adj); [turn on, turn off](#turn-on-turn-off).

### display (v.)
Don't use *display* when you mean *appear*.

> Correct: The Print dialog appears.
> Incorrect: The Print dialog displays.

See also [appear](#appear).

### do
Don't use in phrases such as *do a clean installation*. Use *perform* instead.

### enable (v.), enabled (adj.)
Avoid when you mean *turn on*. *Turn on* implies initiating an action or starting a process immediately; *enable* implies doing a task that makes subsequent actions possible.

> Correct: Turn on Windows file sharing.
> Incorrect: Enable Windows file sharing.

Don't use *enabled* when you mean *selected* (for example, when you refer to radio buttons or checkboxes) or *available* (when you refer to commands or buttons that are sometimes dimmed, but not in this case).

> Correct: Make sure the Use Touch ID checkbox is selected in Notes settings.
> Incorrect: Make sure the Use Touch ID option is enabled in Notes settings.
> Correct: The Copy command isn't available because no text is selected.
> Incorrect: The Copy command isn't enabled because no text is selected.

Don't use *enable* when you mean *give the ability to*. You can usually rewrite a sentence to avoid it.

> Correct: With iMovie, you can view, edit, and share movie projects.
> Incorrect: iMovie enables you to view, edit, and share movie projects.

It's OK to use *enable* to describe a task that makes other actions possible.

> To use this website, you must enable cookies.

See also [allow](#allow); [disable (v.), disabled (adj.)](#disable-v-disabled-adj); [let](#let).

### enter
Use *enter*, not *type*, to describe inputting text-based information by typing, copying and pasting, dragging, or some other method. Use *type* to describe pressing or tapping keys to produce characters on the screen. Use *press*, not *type*, to refer to pressing keys on the keyboard.

> Enter your account information and tap Save.
> The intelligent keyboard may suggest corrections as you type.
> Press the Return key.

See also [press](#press); [type (v.)](#type-v).

### entitled
Don't use; use *titled*, *named*, or *called*.

### exit
In user materials, don't use to refer to quitting an open app; use *quit*. See also [interrupt](#interrupt); [quit](#quit); [stop](#stop).

### first person
Don't use the first-person pronouns *we*, *us*, or *I*; rewrite in terms of the reader or the product.

### force click (v.)
Use to describe the act of pressing a Force Touch trackpad until you feel a deeper click.

> Force click a file's icon to see a quick preview of the file.

See also [click and hold](#click-and-hold); *Force Touch*.

### force quit
In user materials, it's preferable to say *force an app to quit*.

> Acceptable: If an app doesn't respond, you can force quit it.
> Preferable: If an app doesn't respond, you can force it to quit.

### freeze
Use to refer to the behavior of a pointer on the screen. Avoid using *freeze* as a noun or to refer to something the computer does. Instead, use a phrase such as *not responding*.

> Correct: If the pointer freezes, or if the computer stops responding to the mouse, trackpad, or keyboard, follow these instructions.
> Incorrect: If the computer freezes, follow these instructions.
> Incorrect: If you experience a freeze, follow these instructions.

### front, frontmost
The active window is the *front* or *frontmost* window. See also [active](#active); [in front](#in-front).

### functionality
In user materials, avoid if you can use a word such as *features* instead.

> Avoid: Some functionality is not available in certain regions.
> Preferable: Some features are not available in certain regions.

### future tense
Whenever possible, use present, not future, tense. Don't switch unnecessarily from present to future tense when present tense is sufficient to express a sequence of steps or events.

- *Conditional constructions:* Use present tense for conditional constructions such as the following:

> Correct: If the noWait parameter is true, play from the disk stops immediately, and program control returns to the caller.
> Incorrect: If the noWait parameter is true, play from the disk will stop immediately, and program control will return to the caller.

- *Future events:* Future tense is sometimes appropriate—for example, when a product described isn't yet available.

> Apple will give users a peek at the new app by releasing a public beta.
> Next year students at Clareton High School will use EPUB textbooks in their math classes.

### hang
Don't use as a description of the computer's behavior in response to a system error; use a phrase such as *not responding*.

> Correct: If the computer doesn't respond to input from the mouse, trackpad, or keyboard, a system error may have occurred.
> Incorrect: If the computer hangs, a system error may have occurred.

See also [freeze](#freeze).

### highlight (v.)
Don't use when you mean *select*.

> Correct: Select the text you want to change.
> Incorrect: Highlight the text you want to change.

Don't use as an intransitive verb.

> Correct: As you type in the search field, matching icons are highlighted in the window below.
> Incorrect: As you type in the search field, matching icons highlight in the window below.

See also [highlighted (adj.)](#highlighted-adj); [highlighting (n.)](#highlighting-n); [select (v.)](#select-v).

### hit (v.)
Don't use to instruct users to press a key or touch a screen; use *press* or *tap* instead. See also [press](#press); [tap (n., v.)](#tap-n-v).

### hold down
Don't use to describe the act of pressing the mouse or trackpad, a key on the keyboard, or a mechanical button until an action or result occurs. Use *press and hold*. See also [press and hold](#press-and-hold).

### hover (v.)
Avoid using *hover over* to describe the act of holding the pointer over an onscreen element until something occurs. Use *hold the pointer over* or *move the pointer to* instead.

> Correct: Hold the pointer over an address, and then click the arrow that appears.
> Correct: Move the pointer to the right of Auto-Play, click the pop-up menu, and then choose an option.
> Avoid: Hover over a participant's name, and then click the More button.

Don't use *hover the pointer over*.

See also [Apple Pencil hover](apple-features-software.md#apple-pencil-hover); [Hover Text](apple-features-software.md#hover-text).

### if necessary
Avoid in user materials. Instead, describe the circumstance in which the action would be necessary.

> Correct: If file sharing isn't on, turn it on.
> Incorrect: If necessary, turn on file sharing.
> Correct: If the file size is larger than the maximum your mail app allows, compress the file.
> Incorrect: If necessary, compress the file.

### if, whether
Use *if* to indicate a condition. Use *whether* when two outcomes are possible.

If you can mentally introduce the words *or not* in a clause, use *whether* rather than *if*.

> Correct: When you start editing a locked file, the app asks whether you want to unlock it.
> Incorrect: When you start editing a locked file, the app asks if you want to unlock it.

Although using *if* specifies a condition, it can also introduce ambiguity. For instance, *Let her know if he sets up the user account* may mean either *Let her know whether he sets up the user account* or *If he sets up the user account, let her know*. Ensure that the condition's meaning is clear.

### in front
Use to explain the term *active* (*the active window is in front of other windows*); subsequently, use *active*. You can also use to describe windows that "float" on top of active windows. See also [active](#active); [front, frontmost](#front-frontmost).

### in order to
Don't use unless absolutely necessary; use just *to*.

### input (n., adj.)
Avoid using as a verb; instead, use *enter* or *type*, depending on the context.

### inside
Not *inside of*.

### interrupt
OK to use as a noun in developer materials. See also [exit](#exit); [force quit](#force-quit); [quit](#quit); [stop](#stop).

### kill
Don't use to refer to stopping an app or process. Use an alternative that conveys the correct meaning in context, such as *force quit*, *force exit*, *terminate*, *end*, *stop*, *halt*, or *cancel*.

> Correct: Cancel all background tasks.
> Incorrect: Kill all background tasks.

If the term *kill* is used in code you're documenting and the code can't be changed, show a code sample to make it clear what users need to enter, but use alternative terms in the documentation.

### launch
Avoid in user materials when you mean to *open* an app. OK to use in developer materials.

### let
Don't overuse the phrase *lets you* in instructions; try to restructure the sentence to focus on what the user does.

> Avoid: The Up Next button lets you see which songs will play next.
> Preferable: Click the Up Next button to see which songs will play next.

It's OK to use *lets you* in content that focuses on describing features and their capabilities.

> Family Sharing lets you share Apple purchases and subscriptions with family.

See also [allow](#allow); [disable (v.), disabled (adj.)](#disable-v-disabled-adj); [enable (v.), enabled (adj.)](#enable-v-enabled-adj).

### like, love
Users can *like* or *love* an item. Items can have *likes*, but not *loves*; instead, refer to loved items as *items you've loved* or *loved items*. Users can *dislike* a liked or loved item. Don't capitalize *like* or *love* unless you're referring to a button in the user interface (for example, *the Loved button*).

To avoid ambiguity, you can also say *mark an item as liked*, an item *is marked as loved*, or similar.

### localizable
Don't use.

> Correct: An app that follows the human interface guidelines should be easy to localize.
> Incorrect: An app that follows the human interface guidelines should be easily localizable.

### localize (v.)
Takes the preposition *for*, not *to*.

> Correct: Whether you localize your app for the French language or for French Canada, make sure you test its interface.

### look
Use to refer to looking at buttons and elements in visionOS to interact with them. Don't use *gaze*.

> App icons subtly come to life when you look at them.

In visionOS, looking at an element is an integral part of interacting with it, so you don't need to include *look* with every instruction. However, when you're first explaining how to do something on Apple Vision Pro, you can include *look* to help describe the action.

> First reference: To open an app, look at the app and tap your fingers together.
> Subsequent references: Tap an app to open it.

### mount (v.)
In user materials, avoid when referring to making a disk or disk image available; use alternatives such as *open*, *make available*, or *connect to*, or describe what the user must do to make the disk available.

> Avoid: To see the contents of a disk image, you must mount the disk image.
> Preferable: To see the contents of a disk image, you must open the disk image by double-clicking it.

In server materials or materials for more technical users, it's OK to use *mount*.

Don't use *mount* as an intransitive verb.

> Correct: Mount the volume.
> Incorrect: The volume mounts.

See also [unmount (v.)](#unmount-v).

### native
In user materials, avoid using *native* to describe apps; instead, describe the apps as being designed to work with specific hardware or software.

> For best performance, use an app designed for use on Intel-based Mac computers.

### new
In most documents, avoid describing a product or feature as new because the text will quickly become out of date. When appropriate, state the version of software in which a feature was introduced.

> Correct: Auto Unlock, introduced with macOS Sierra 10.12…
> Incorrect: The new Auto Unlock feature…

### once
Don't use when you mean *after*.

> Correct: After you turn on the computer…
> Incorrect: Once you turn on the computer…

### open
Users *open* icons, folders, documents, and apps. See also [close](#close).

### optionally
Avoid in user materials. Instead, describe the reason the user would perform the action. If it's important to emphasize that the action is optional, you can say *If you want to…*

> Correct: If you want to set a disk quota, enter the number and specify megabytes (MB) or gigabytes (GB).
> Incorrect: Optionally, enter a disk quota and specify megabytes (MB) or gigabytes (GB).

### passive voice
Avoid when possible and use active voice. Passive voice is sometimes appropriate and necessary—for example, when using the active voice would require either a highly convoluted sentence structure or excessive anthropomorphism—but rewrite to avoid passive voice if you can.

In tutorials, a passive construction might be appropriate to avoid miscuing the reader—that is, when you describe an action that the user isn't supposed to try yet.

> Explanation screen: An icon is selected by clicking it.
> User-try screen: You try it. Click the icon.

### please
Avoid using *please* in instructional text and cross-references.

> Correct: Follow the steps below.
> Incorrect: Please follow the steps below.
> Correct: For more information, see "Store Settings" on page 96.
> Incorrect: For more information, please see "Store Settings" on page 96.

### point (v.)
When you describe the desktop interface, avoid using *point* as a verb. Instead, use *move the pointer to* or similar wording.

> Avoid: Point to an item to see a description of what you can do with it.
> Preferable: Hold the pointer over an item to see a description of what you can do with it.

### press
Use to describe the act of pressing and quickly releasing keys on the keyboard and mechanical buttons and switches. Don't use *click*, *hit*, *push*, *tap*, or *type*.

> Correct: Press the Return key.
> Correct: Press the power button.
> Incorrect: Type your password and hit the Return key.

You can also use *press* to describe the act of pressing the stem on some models of AirPods.

- Don't use *press* to refer to onscreen items; use *click*, *force click*, or *click and hold*.

> Correct: Click and hold an icon in the Dock until a menu appears.
> Correct: Force click an address to see it on a map.
> Incorrect: Press an icon in the Dock until a menu appears.

- Don't use *press* when you mean *press and hold*.

> Correct: Press and hold the C key while you restart the computer.
> Incorrect: Press the C key and restart the computer. [It's not clear that you need to keep pressing.]

- Don't say *press and drag*; simply say *drag*.

See also [click](#click); [enter](#enter); [tap (n., v.)](#tap-n-v); [type (v.)](#type-v).

### press and hold
Use *press and hold* (not *hold down*) to describe the act of pressing the mouse or trackpad, a key on the keyboard, or a mechanical button until a specified action or result occurs.

Don't use *press and hold* when you mean *press*, which means to press and quickly release a key or mechanical button.

> Correct: To restart your Mac, press and hold the power button.
> Incorrect: To restart your Mac, press the power button.

Don't use *press and hold* when you mean *click and hold*. *Click and hold* refers to using the mouse or trackpad to interact with onscreen items; *press and hold* refers to interacting with the physical mouse or trackpad itself.

See also [click and hold](#click-and-hold); [press](#press); [touch and hold](#touch-and-hold).

### prompt (n., v., adj.)
Avoid using *prompt* as a verb if you can simply tell users to do something, or if you can use friendlier wording such as *when asked* or *you may be asked*.

> Avoid: Double-click the side button, and then enter your passcode when prompted.
> Preferable: Double-click the side button, and then enter your passcode.

If you do use *prompt*, don't make hardware or software the actor; instead, use passive voice.

> Correct: If you select Image, you're prompted to select an image file.
> Incorrect: If you select Image, the app prompts you to select an image file.

It's OK to use *prompt* as a noun or an adjective when referring to the prompt character in a command-line interface.

### push
Don't use to refer to the act of pressing a button or a key on a keyboard; use *press*. See also [press](#press).

Don't use *push* when discussing services (such as iCloud) that send content to devices automatically; instead, say content *appears automatically* or *is updated*.

> iCloud updates your photos on all your devices.

### put
Don't use when you mean *drag*.

> Correct: Drag the file to the Trash.
> Incorrect: Put the file in the Trash.

### quit
Use *quit* to refer to stopping an app from running completely. Don't use *exit*, *exit from*, or *leave* when you mean *quit*. See also [close](#close); [force quit](#force-quit); [interrupt](#interrupt); [stop](#stop).

### recommend
When describing something users are encouraged to do, don't use *we recommend* or *Apple recommends*; use *recommended*.

> Correct: It's recommended that you import video using the same camera you used to record it.
> Incorrect: We recommend that you import video using the same camera you used to record it.

You can also use less formal phrases like *it's a good idea to*.

> It's a good idea to create a password hint.

### reference
Don't use as a verb; use *refer to*.

### regular
Don't use when you mean *standard*, as in *Use standard settings*.

### restart (v.)
Don't use as a noun.

### restore (v., adj.)
Don't use as a noun.

> Correct: Avoid stopping the restore process.
> Incorrect: Avoid stopping a restore in progress.
> Correct: Restoring stopped because the disk is full.
> Incorrect: The restore stopped because the disk is full.

### run (v.), running (adj.)
Use *running* for programs or processes that operate in the background and have no graphical interface.

> Open Activity Monitor to see what processes are running.

- *Apps:* Don't use *run* to describe what a user does with an app (a program that has a graphical interface); say *use* instead.

> Correct: Before installing the software, use Disk Utility to verify your disk.
> Incorrect: Before installing the software, run Disk Utility.

Don't use *running* to refer to an open app; use *open*.

> Correct: Check to see whether any apps are open.
> Incorrect: Check to see whether any apps are running.

- *Software versions:* In user materials, avoid using *running* to refer to versions of the operating system or apps. Instead, use alternatives such as *use*, *using*, or *installed*. In server materials or materials for more technical users, it's OK to use *running* to refer to versions of the operating system or apps.

> Correct: If you're using iOS 12 or earlier, follow these instructions.
> Incorrect: If you're running iOS 12 or earlier, follow these instructions.

### scroll
Avoid using as a transitive verb.

> Correct: Scroll through a document.
> Correct: Scroll to view more of the document.
> Incorrect: Scroll a document.

In user materials, when describing the act of moving through documents, webpages, groups of options, and other items, it's often preferable to use *scroll* instead of specific actions and gestures such as *drag* or *swipe*.

> Acceptable: Drag up or down to scroll through the songs in the list until you find the one you want.
> Preferable: Scroll through the songs in the list until you find the one you want.

### select (v.)
Use *select*, not *choose*, to refer to the action users perform when they select among multiple objects—such as icons, graphic images, radio buttons, or checkboxes—or when they highlight text for editing.

> Select a name in the list.
> To select several files at once, Command-click them.
> Select the text you want to make bold.
> Select the Shadow checkbox.

Use *choose* for menu items, including those in pop-up and shortcut menus.

See also [checkbox](ui-elements.md#checkbox); [choose](#choose); [click](#click); [deselect](#deselect); [highlight (v.)](#highlight-v); [menus](ui-elements.md#menus); [unselected (adj.)](#unselected-adj).

### shows up
Don't use; use *appears*. OK to use *show* when referring to showing and hiding onscreen elements.

> The Portrait Lighting slider appears below the frame.
> To show a hidden photo, choose View > Hidden Photos.

### slide (v.)
Avoid when describing how users operate a slider or switch. Use *tap*, *click*, or *drag* instead.

> Correct: To increase or decrease the effect, drag the slider.
> Incorrect: To increase or decrease the effect, slide the slider.
> Correct: Tap the switch to turn Airplane Mode on or off.
> Incorrect: Slide the switch to turn Airplane Mode on or off.

It's OK to use other meanings of *slide*, in other contexts.

### start
Don't use when you mean *open* (as in *open an app*).

### stop
A general term meaning to cause a process, command, or program to cease. Don't use when you mean *quit an app*. See also [exit](#exit); [interrupt](#interrupt); [quit](#quit).

### support
Avoid in user materials when you can use *compatible*, *works with*, or another appropriate word or phrase.

> Avoid: The first-generation iPad didn't support AirPlay Mirroring.
> Preferable: AirPlay Mirroring works with iPad 2 or later.
> Avoid: iMovie supports most QuickTime formats.
> Preferable: You can use files in most QuickTime formats with iMovie.

It's OK to use *support* to refer to a product or feature that Apple doesn't provide but that the user can obtain (for example, using software from other manufacturers). Avoid saying *Apple doesn't support* something.

### tap (n., v.)
On devices with touchscreens or trackpads, *tap* refers to the act of quickly touching and releasing the touchscreen or trackpad. Don't use *tap on*.

> Correct: Tap Return to move from one field to another.
> Incorrect: Tap on the video you want to play.

Users can tap with one or more fingers (depending on the device and the action the user is performing).

> To zoom in or out, double-tap with two fingers.

On Apple Vision Pro, *tap* refers to the act of briefly tapping your thumb and finger together. See also [pinch (v.)](#pinch-v).

When discussing the Digital Touch feature, don't say that users *tap* another device or person; they *send a tap*.

When discussing haptic feedback, don't say that a device or trackpad *taps you*; say *you feel a tap*.

### tap and hold
Don't use. *Tap* means to touch and release quickly, so use *touch and hold* instead. See also [tap (n., v.)](#tap-n-v); [touch and hold](#touch-and-hold).

### that
Use to introduce a restrictive clause; clauses beginning with *that* are generally not set off with commas.

> This is the computer that has network access.
> The newest computer in the lab, which is a Mac Pro, is also the students' favorite.

See also [which](#which).

### throw away
Don't use when you mean *drag an item to the Trash*.

> Correct: After you've expanded the compressed file, drag it to the Trash.
> Incorrect: Throw away the compressed file after you expand it.

### toggle (v.)
OK to use in developer materials. Don't use in user materials; instead, say *turn on or off*, *switch between*, or whatever wording is appropriate in the context.

See also [switch (v.)](word-choice-and-confusables.md#switch-v).

### touch and hold
Refers to the act of touching a touchscreen and leaving the finger motionless until an action or result occurs.

> Touch and hold the Mute button to hold a call.

Don't use *tap and hold*. Don't use *long press* in user materials (it's OK in developer materials).

See also [click and hold](#click-and-hold); [gestures](#gestures); [long press (n.), long-press (adj.)](#long-press-n-long-press-adj); [tap (n., v.)](#tap-n-v).

### turn on, turn off
OK to use when you describe power to a computer or peripheral device. You can also use *turn on* to describe enabling features such as file sharing, as in *turn on file sharing*. See also *startup (n., adj.), start up (v.)*.

### type (v.)
Use to describe the act of pressing keys to produce characters on the screen. Use code font or quotation marks to represent what the user actually types, depending on your department's style guidelines.

> In the Title field, type Exchange Rate per $1.
> For example, type "dog" in the search field to find photos of dogs.

Use regular text font to describe generically what the user types.

> Type a new timecode value and press Return.

Don't use *type in* when you mean *type*. See also [enter](#enter); [press](#press).

### we
Don't use first person; rewrite in terms of the reader or the product.

> Correct: For best results, the image should be at least 600 x 600 pixels.
> Incorrect: We recommend that the image be at least 600 x 600 pixels.

See also [recommend](#recommend).

### which
Use only to introduce a nonrestrictive clause; clauses beginning with *which* are always set off with commas.

> The newest computer in the lab, which is a Mac Pro, is also the students' favorite.
> This is the computer that has network access.

See also [that](#that).

### while, although, whereas
*While* means *during the time that* and implies concurrent activities. Use *although* to mean *in spite of the fact that*. Use *whereas* to mean *it being the fact that* or *while on the contrary*.

> Correct: Although the clip won't play back at 1x (normal) speed, every frame plays back, with no frames dropped.
> Incorrect: While the clip won't play back at 1x (normal) speed, every frame plays back, with no frames dropped.
> Correct: SD video uses interlaced scanning, whereas HD formats may use either interlaced or progressive scanning.
> Incorrect: SD video uses interlaced scanning, while HD formats may use either interlaced or progressive scanning.

### who, whom
*Who* should always be used as the subject of a verb or as a subject complement. *Whom* should always be used as the object of a verb or preposition.

> Who is the new system administrator?
> This manual is intended for the person who manages the network.
> Be selective about the people to whom you give network access.

### wish
Don't use; use *want*. See also [want](#want).

### unmount (v.)
In user materials, avoid when referring to making a disk or disk image unavailable; use alternatives such as *eject* or *make unavailable*, or describe what the user must do to make the disk unavailable.

> Avoid: Unmount the disc when you finish using it.
> Preferable: Eject the disc when you finish using it.

In server materials or materials for more technical users, it's OK to use *unmount*.

Don't use *unmount* as an intransitive verb.

> Correct: Unmount the volume.
> Incorrect: The volume unmounts.

See also [mount (v.)](#mount-v).

### want
Make sure that an object follows the verb *want*.

> Correct: Make a copy if you want a duplicate. [The word *duplicate* is the object.]
> Correct: Sign up if you want to attend. [The infinitive, *to attend*, is the object.]

You can often avoid the issue entirely. For example, *If you want to introduce alternative methods* can be changed to *To introduce alternative methods*.

### user
If the audience of your document consists of users, avoid this term. Instead, address the reader as *you*.

> Correct: You can make movies with effects and a soundtrack.
> Incorrect: Users can make movies with effects and a soundtrack.

When the audience consists of developers or administrators, use *user* to refer to end users and *you* to address the developer or administrator.

> You may need to prevent users from accidentally making changes.
> You can give users access to the server.

*User* is also appropriate in the context of macOS users—for example, when you discuss Users & Groups settings in macOS.

See also [end user (n.), end-user (adj.)](#end-user-n-end-user-adj).

### end user (n.), end-user (adj.)
Avoid in favor of *user*. See also [user](#user).

### deselect
OK to use when you mean *cancel a selection*. Not *uncheck*, *unselect*, *unhighlight*, or *dehighlight*. See also [checkbox](ui-elements.md#checkbox); [radio button](ui-elements.md#radio-button); [unselected (adj.)](#unselected-adj).

### unselected (adj.)
Use to describe something that's not selected. Not *deselected*, *unchecked*, or *dehighlighted*. See also [checkbox](ui-elements.md#checkbox); [deselect](#deselect); [unhighlighted (adj.)](#unhighlighted-adj).

### unhighlighted (adj.)
Don't use; use *not highlighted*. See also [unselected (adj.)](#unselected-adj).

### unhighlight (v.)
Don't use. Use *deselect* for the action of clicking to remove highlighting.

### highlighted (adj.)
Not *hilighted*. Don't use *inverted* except in developer materials. When explaining highlighting, use *a highlighted icon changes color* or *a highlighted icon is filled in*.

> Correct: When you click the icon, it becomes highlighted.
> Incorrect: When you click the icon, it highlights.

Don't use *unhighlighted* or *dehighlighted* for an item that isn't highlighted; use *not highlighted*.

### highlighting (n.)
Don't use in user materials. OK to use in developer materials.

> When an app displays a selection range, it marks the range with highlighting.

### gestures
Refers to finger movements used on a touchscreen or trackpad or with Apple Vision Pro. Don't refer to them as *finger gestures*; use simply *gestures*.

When you write instructions that include gestures, in general, don't include the word *finger*.

> Correct: Swipe left or right.
> Incorrect: Swipe your finger left or right.

However, you can refer to fingers if the gesture involves multiple fingers or is complex.

> Triple-tap with two fingers.
> Touch and hold the object with one finger, and use another finger to swipe in the direction you want the object to move.

You can also refer to fingers to provide greater detail when you first define or describe a gesture; subsequent occurrences can omit *finger*.

> Defining reference: Pinch two fingers together or apart to zoom out or in.
> Other occurrences: Pinch to zoom in on the page.

When describing the act of scrolling through documents and other items, it's often preferable to simply use *scroll* instead of specific gestures such as *drag* or *swipe*.

See also [drag](#drag); [pinch (v.)](#pinch-v); [rotate](#rotate); [scroll](#scroll); [swipe (n., v.)](#swipe-n-v); [tap (n., v.)](#tap-n-v); [touch](#touch); [touch and hold](#touch-and-hold).

### drag
Refers to an action that can be performed on a desktop or laptop computer, on a device with a touchscreen, or on Apple Vision Pro. Usage is slightly different in each case; follow the guidelines below.

- *On desktop and laptop computers:* Drag refers to the act of positioning the pointer, pressing and holding the mouse or trackpad, moving the mouse (or, on a trackpad, the user's finger), and then releasing. If you're writing for novice users, you might need to define *drag* on first mention.

Use *drag* to refer to actions users perform with objects onscreen. Don't use *drag the mouse* or *drag the pointer*.

> Correct: Drag the Volume slider to change the volume.
> Correct: Choose Tools > Annotate > Rectangle, and then drag to create a rectangle.
> Incorrect: Drag the mouse to draw a rectangle.

Don't use *click and drag*. Don't use *place*, *put*, or *move* when you mean *drag*.

> Correct: Drag your songs into the order you want.
> Correct: Drag the icon to the Trash.
> Incorrect: Click and drag the icon to the Trash.
> Incorrect: Put the icon in the Trash.

- *On devices with touchscreens:* Drag refers to the act of moving one finger across the screen.

Users can drag to scroll through items, drag controls, or drag to pan around items such as photos and webpages.

> Drag up or down to scroll through your contacts.

Don't use *tap and drag*. Don't say *drag your finger*.

- *On Apple Vision Pro:* Drag refers to the act of pinching and holding your thumb and finger together to select an object, and then moving your hand to drag the object. In instructions for users, in most cases use *pinch and drag* (not just *drag*).

See also [gestures](#gestures); [swipe (n., v.)](#swipe-n-v).

### pinch (v.)
Refers to a gesture that can be performed on a device with a touchscreen or trackpad, or on Apple Vision Pro. Usage is slightly different in each case; follow the guidelines below.

- *On devices with touchscreens or trackpads:* Pinch refers to the act of placing two fingers on the touchscreen or trackpad and then moving them closer together or farther apart.

> Pinch the photo to zoom in or out.

In most cases, you can use just *pinch*, but if you need to describe the motion in more detail, you can use *pinch open* to describe moving the fingers apart and *pinch closed* for moving the fingers together. (Note that developer materials use *pinch close*.)

- *On Apple Vision Pro:* Pinch refers to the act of pinching and holding your thumb and finger together.

Use *pinch and hold* to refer to pinching an element or control in the interface until additional options appear.

Use *pinch and drag* to refer to pinching an object and dragging to move it, and *pinch and scroll* to refer to pinching and scrolling through content, lists of options, and so on.

### rotate
Refers to the act of placing two fingers slightly apart on a touchscreen or trackpad and twisting them clockwise or counterclockwise.

> Rotate to change the photo's orientation.

Don't use to refer to turning the Digital Crown; use *turn*.

### swipe (n., v.)
On devices with touchscreens or trackpads, *swipe* refers to the act of quickly sliding one or more fingers across the touchscreen or trackpad. On Apple Vision Pro, *swipe* refers to the act of pinching your thumb and finger together and quickly flicking your wrist.

Users swipe to navigate documents, webpages, and areas of the interface, and to browse lists and groups of items. Include the direction of the swipe—up, down, left, or right—if it's needed to describe the action.

> Tap the movie, and then swipe to choose a duration.
> Swipe left to read the next story.
> Swipe down from the top-right corner to open Control Center.

You can use prepositions such as *over* and *on* to make it clear where to swipe.

To describe swiping with more than one finger, say, for example, *swipe with two fingers* (for the verb form) or *two-finger swipe* (for the noun form).

### touch
In visionOS, it's OK to use *touch* when referring to interacting directly with virtual objects (such as the virtual keyboard).

> To type on the virtual keyboard, touch the keys; touch and hold a key to show special characters and accents.

See also [tap (n., v.)](#tap-n-v).

### sync, synced, syncing
Not *synch*, *synched*, or *synching*.

In general, *syncing* refers to copying content directly between two devices. You can use *sync* to refer to syncing devices or the content that's on them.

Don't use *synchronize* or *synchronization* as alternative terms for *sync* or as an explanation of the term *sync*.

> Correct: Make sure syncing is turned on for the device.
> Incorrect: Make sure synchronization is turned on for the device.

### output (n., adj.)
Avoid as a verb; use *write to*, *display on*, *print on*, or *print to*.

### output (use)
Don't use as a verb.

### long press (n.), long-press (adj.)
In developer materials, you can use *long press* when discussing the gesture recognizer that detects when a user touches and holds an onscreen item.

Don't use *long press* in user materials. Instead, use *press and hold* to refer to the act of pressing a mechanical button until an action or result occurs; use *touch and hold* to refer to the act of touching a touchscreen and leaving the finger motionless until an action or result occurs.

See also [press and hold](#press-and-hold); [touch and hold](#touch-and-hold).
