Help:Contents - Revision history

Stownsend at 14:48, 18 March 2016

2016-03-18T14:48:35Z

2016-03-09T17:34:46Z

‎Glossary for Protocase Designer Wiki Editors

2016-03-09T17:19:30Z

2016-03-09T17:14:20Z

‎Protocase Designer Glossary

2016-02-02T13:56:01Z

‎Mouse Terms

2016-02-02T13:41:05Z

‎Toolbars

2016-02-01T16:14:30Z

‎Protocase Customer-facing Email Addresses and Group References

2016-02-01T16:03:53Z

‎Protocase Email Addresses and Group References

2016-02-01T15:59:13Z

‎Protocase Email Addresses

2016-01-08T14:56:42Z

‎Procedures

@@ Line 1: / Line 1: @@
-This page is for authors and editors of the Protocase Designer wiki. For help with Designer features and procedures, including Technical Support, see the Help links on the [[Main_Page|'''Home page''']]. For help with definitions of terms, see the Protocase Designer Glossary((topic and link to come)).
+This page is for authors and editors of the Protocase Designer wiki. For help with Designer features and procedures, including Technical Support, see the Help links on the [[Main_Page|'''Home page''']]. For help with definitions of terms, see the [[Glossary | '''Protocase Designer Glossary''']].
 ==Glossary for Protocase Designer Wiki Editors==
 {| border="1" cellpadding="5" cellspacing="0"

@@ Line 27: / Line 27: @@
 |-
 |depth||Parameter||Enter the depth for your enclosure.<br>New Assembly dialog box:<br>Depth<br>Depth: Bottom<br>Depth: Top<br>Depth: Recessed
 |-
 |extrusion||Part||Click the left extrusion to open the Face Editor.

@@ Line 1: / Line 1: @@
+This page is for authors and editors of the Protocase Designer wiki. For help with Designer features and procedures, including Technical Support, see the Help links on the [[Main_Page|'''Home page''']]. For help with definitions of terms, see the Protocase Designer Glossary((topic and link to come)).
 ==Glossary for Protocase Designer Wiki Editors==
 {| border="1" cellpadding="5" cellspacing="0"

@@ Line 1: / Line 1: @@
-==Protocase Designer Glossary==
+==Glossary for Protocase Designer Wiki Editors==
 {| border="1" cellpadding="5" cellspacing="0"
 !Term

@@ Line 149: / Line 149: @@
 *Use ''click'', not ''click on''.
-''Example''
+''Examples''
 :To see the '''Control''' menu, right-click anywhere in the window.
 :Click in the window to make it active.

@@ Line 125: / Line 125: @@
 === Toolbars ===
-*General toolbars contain buttons.
+*General toolbars contain buttons. The '''Drawing''' toolbar contains tools.
-*A toolbar button with a submenu is called a ''menu button''.
+the'' and ''button'' with toolbar buttons.
 *Use lowercase for the word toolbar.
 *Bold toolbar names, buttons, and tools.

@@ Line 93: / Line 93: @@
 !Examples
 |-
-|info@protocase.com <br> or tech@protocase.com||Engineering & Design Services <br> NOTE: Nickname: For customers, NONE. For internal use, "EDS" is OK. ||Everything except orders/ordering or a specific software problem in progress||"Please note: Fonts that appear smaller than Times New Roman and Myriad Pro may have to be enlarged to ensure proper white underbase. Please email info@protocase.com for more information."<br><br>
+|info@protocase.com <br> or tech@protocase.com||Engineering & Design Services <br><br> NOTE: Nickname: For customers, no nickname or initials; always spell out in full. For internal use, "EDS" is OK. ||Everything except orders/ordering or a specific software problem in progress||"Please note: Fonts that appear smaller than Times New Roman and Myriad Pro may have to be enlarged to ensure proper white underbase. Please email info@protocase.com for more information."<br><br>
 "Tighter tolerances are possible; if this is necessary, please email info@protocase.com."
 |-

@@ Line 86: / Line 86: @@
 <br><br>
-==Protocase Email Addresses==
+==Protocase Email Addresses and Group References==
 {| border="1" cellpadding="5" cellspacing="0"
 !Address

@@ Line 176: / Line 176: @@
 #List prerequisites
 #Highlight hazards
-#Write the steps.
+#Write the steps
 #*Use clear, present tense imperatives
 #**e.g. Set the starting time vs. Users should select a starting time
 #*Keep sentences short
 #*Make sure you can perform each step
 #*Unless the procedure is explaining one specific task, write the ''best'' way, not every way (menus, buttons, etc.).