Spellchecking

1. Place the caret at any word highlighted by the Typo inspection.

2. Click or press AltEnter to show the available intention actions.

3. Select one of the suggested fixes from the list.

In string literals and comments, only the spelling of this particular word at caret changes. For code elements, such as names of variables, functions, classes, and other symbols, the inspection also suggests changing all occurrences via the Rename refactoring.

If a detected typo is actually a valid word, you can add it to a user-defined dictionary that extends the built-in dictionaries.

1. Place the caret at a word highlighted by the Typo inspection.

2. Click or press AltEnter to show the available intention actions.

3. Select the Save to dictionary action to add the word to the user's dictionary and skip it in the future.

   If you have added the word by mistake, press Ctrl0Z to remove it from the dictionary.

By default, PhpStorm saves words to the global application-level dictionary. You can choose to save words to the project-level dictionary if the spelling is correct only for this particular project. For more information, refer to Select the default dictionary for saving words.

The Typo inspection highlights typos in the current file. You can also run the inspection on your entire project or a set of files. For more information, refer to Run a single inspection.

1. Go to Code | Analyze Code | Run Inspection by Name… or press CtrlAltShift0I.

2. In the Enter inspection name popup, find and select the Typo inspection.

3. In the Run 'Typo' dialog, select the scope in which you want to run the inspection, and other options, such as a file mask filter. Then click OK.

PhpStorm will run the Typo inspection on all files in the selected scope and show all found typos in a separate tab of the Problems tool window.

By default, the Typo inspection checks all text, including code elements, string literals, and comments in all scopes.

1. Press CtrlAlt0S to open the IDE settings and then select Editor | Inspections.

2. Expand the Proofreading node and click Typo in the central pane.

3. In the right-hand pane, configure the Typo inspection:

   Severity

   Specify the severity level and the scope in which to apply this level.

   For example, if you want typos to stand out more, select Error or Warning to highlight typos similar to syntax errors or warnings in your code.

   Options

   Specify the type of content to check:

   • Process code: check various code elements.

   • Process literals: check text inside string literals.

   • Process comments: check text inside comments.

To disable the Typo inspection entirely, clear the checkbox next to it.

Like with any other inspection, you can suppress the Typo inspection for specific files and code elements.

1. Place the caret at a word highlighted by the Typo inspection.

2. Click or press AltEnter to show the available intention actions.

3. On one of the suggested fixes, press the right arrow key or click and select Suppress for file or another relevant suppress action.

   

Depending on the language and code element, this adds a special annotation or comment that tells the editor to suppress the relevant inspection in the corresponding scope. For example, in case of PHP, suppressing the Typo inspection for a class adds the following commented out annotation at the top of the file:

/** @noinspection SpellCheckingInspection */

This suppresses all spelling checks within the file scope.

For more information, refer to Suppress inspections.