Changeset 1124 for specdomain/trunk/src/specdomain/doc/style_guide.rst
- Timestamp:
- Oct 1, 2012 1:08:46 PM (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
specdomain/trunk/src/specdomain/doc/style_guide.rst
r1113 r1124 25 25 throws readers out of their rhythm when they go to read it. Avoid this. 26 26 27 With these words in mind, this style guides documents the conventions set forth28 t o use for SPEC macros at the APS.27 With these words in mind, this SPEC Documentation Style Guide documents 28 the conventions set forth to use for SPEC macros at the APS. 29 29 30 30 The concept of docstrings … … 178 178 It is recommended to build up this section as a definition list. The headings 179 179 for each item are CAPITALIZED and end with a colon. The content under each of 180 these items should be indented one level. This results in a more l eightweight180 these items should be indented one level. This results in a more lightweight 181 181 layout, and prevents cluttering the tables of content with too many 182 182 subsections. 183 183 184 The following items should be included, prefer rably in this order:184 The following items should be included, preferably in this order: 185 185 186 186 * AUTHOR(S): … … 193 193 * KNOWN BUGS: 194 194 195 See the below examplefor more details on each of these items.195 See the example below for more details on each of these items. 196 196 197 197 … … 278 278 279 279 Copyright (c) 2010-|current_year|, UChicago Argonne, LLC 280 280 Operator of Argonne National Laboratory 281 281 All Rights Reserved 282 282 283 283 APS SPEC macros 284 285 APS SPEC development team,286 X-ray Science Division and APS Engineering Support Division,287 Argonne National Laboratory288 284 289 285 LICENSE:: … … 321 317 322 318 Neither the United States GOVERNMENT, nor the United States Department 323 of Energy, NOR uchicago argonne, LLC, nor any of their employees, makes319 of Energy, NOR UChicago Argonne, LLC, nor any of their employees, makes 324 320 any warranty, express or implied, or assumes any legal liability or 325 321 responsibility for the accuracy, completeness, or usefulness of any … … 389 385 indicate that they should be replaced by actual values in the macro call. 390 386 Optional arguments are additionally enclosed in square brackets (``[]``). 391 The actual USAGE syntax should appear as pre formatted text, and each input387 The actual USAGE syntax should appear as pre-formatted text, and each input 392 388 line should start with a "``>``"-symbol to represent the SPEC command line 393 389 prompt::
Note: See TracChangeset
for help on using the changeset viewer.