Fix spelling as you write a task
A runner reads your description literally, so a typo in a name or a term can send it the wrong way. The task description box and the comment box check your spelling as you type: a misspelled word gets a red wavy underline. The check is your browser's own, in the languages your browser is set to check.
Who can do this: anyone who can create tasks or comment on them.
- Open a task's description: select New task on the board for a new one, or open a task and edit it on its Task tab.
- Type the description. A word the browser doesn't know gets a red wavy underline once you move past it.
- Right-click the underlined word. Your browser's menu lists its suggestions at the top.
- Select the right word. It replaces the misspelled one in place.
- If the word is right, such as a product name or a teammate's name, choose your browser's option to add it to its dictionary, so it is no longer underlined anywhere.
- Put code, commands, file names and other exact text in code formatting: wrap it in backticks, or use a code
block. Code is never spell-checked, so
npm cior a variable name stays free of underlines. - Write a comment the same way: the comment box on a task's Comments tab checks spelling too.
No underlines at all? Check that spell checking is on in your browser's settings, and that the language you write in is one it checks. The underlines are only on your screen: nothing is saved or sent with them.
Related
- Write a good task description: what to put in a description so a runner gets it right.
- Edit a task: change a task's description after you created it.
- Format a comment and attach files: bold, lists, links and code in comments.