From 9a5e2754961252659308c35034ef4f2a06e786a5 Mon Sep 17 00:00:00 2001 From: Rachel Nabors Date: Wed, 5 Feb 2020 16:24:59 +0000 Subject: [PATCH] Update STYLEGUIDE.md --- STYLEGUIDE.md | 7 ------- 1 file changed, 7 deletions(-) diff --git a/STYLEGUIDE.md b/STYLEGUIDE.md index 43b1b23c93d..b86814965e0 100644 --- a/STYLEGUIDE.md +++ b/STYLEGUIDE.md @@ -123,13 +123,6 @@ When it comes to describing property values, be definitive in what is and is not * Capitalize “Hooks.” -### Example - -**Bad** “Open Xcode’s ‘Preferences...’ menu and then click on ‘Components.’” Ambiguous. Relies on reader knowing that “Preferences” is a submenu of “Xcode.” Difficult to read at a glance. - -**Good** “Open **Xcode > Preferences...** and select the **Components** tab.” Path is clearer to pick out from the surrounding copy. - - ## Empathize with readers When writing step-by-step instructions (e.g. how to install something), try to forget everything you know about the topic to attain a "beginner's mindset." Imagine follow the instructions you write, one step at time. Often you will discover that there is implicit knowledge that you forgot to mention, or that there are missing or out-of-order steps in the instructions. UX research pro tip: ask _someone else_ to follow your instructions and see where they get stuck!