Categories

Our Sponsor

Enter discount code WRITER111 in the shopping
cart and save $50 at ...

Users Online

+ 20 Guests + 1 Bot

Unique Visitors

  • 155820Visitors Total:
  • 1318Visitors TODAY:
  • 1493Visitors Yesterday:
  • 11192Visitors Last Week:
  • February 15, 2013Since:

Member



How to Use Right Chevron (>) Correctly in Procedural Writing


 Powered by Max Banner Ads 

© Ugur Akinci

RIGHT CHEVRON (>) is used in technical documents to denote a SERIES of SEQUENTIAL ACTIONS.If you;re writing a software or hardware manual, the changes are those actions would be “GUI actions,” that is, describing what the user should do on the screen with a mouse, keyboard shortcut, or a tablet pen.

If you first click A and then B (on a screen), you can use the shorthand “click A > B” to express that. It’s a common usage especially for menu items that reveal sub-menu items.

For example:

Instead of saying “click File and then select Open from the drop-down sub-menu,” it’s shorter just to say “click File > Open”. That’s a proper usage of a right chevron.

However, when you are clicking COMMAND BUTTONS (like OK or SAVE), there is no need to use a right chevron since there is subsequent action following that.

That’s why “click > SAVE” is not correct. You can just say “Click SAVE” and that would be just fine.

Some other examples:

APPROPRIATE: Click Save tab.

NOT SO: Click > Save tab. (“Click” is an action. It is not a GUI/screen element.)

APPROPRIATE: Click Tools on the menu bar.

NOT SO: Click Tools > on the menu bar. (“On the menu bar” is a description. It is not a GUI/screen element.)

Share

Leave a Reply

  

  

  


*

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>