/p/condor/home/bin/tocae.pl condor-admin 1234
 
-{seciont: 10 foot view}
+{section: 10 foot view}
 
 You can access the Condor RUST queue from any dept. linux workstation. To setup, add /p/condor/home/rust/bin/sys to your PATH. If you don't have it already, you probably also want to add /p/condor/home/bin to your PATH, since there are some handy scripts in there to help deal with RUST.
 
@@ -120,31 +120,31 @@
 
 If, instead of responding to the last message you sent them, a user decides to send a new RUST query pertaining to an already-open ticket, you can merge the two:
 
-mergea 6283 6289
+  mergea 6283 6289
 
 or
 
-merges 711 713
+  merges 711 713
 
 This aliases will merge ticket #1 into ticket #2. This is the equivalent to
 
-action --queue condor-admin --merge --num1 X --num2 Y
+  action --queue condor-admin --merge --num1 X --num2 Y
 
 or
 
-action --queue condor-support --merge --num1 X --num2 Y
+  action --queue condor-support --merge --num1 X --num2 Y
 
-Resend a ticket to yourself
+{subsection: Resend a ticket to yourself}
 
 To get rust to resend the e-mail for a rust ticket without assigning it to someone else and then re-assigning it yourself:
 
-[acta | acts] <admin rust #> --send email-address
+  [acta | acts] <admin rust #> --send email-address
 
 for example:
 
-acta 1822 --send zmiller@cs.wisc.edu
+  acta 1822 --send zmiller@cs.wisc.edu
 
-Copying off-list email to an existing ticket
+{subsection: Copying off-list email to an existing ticket}
 
 Peter C. provided the scripts "rustmea" and "rustmes" (in /p/condor/home/bin) to take an e-mail message from stdin, and bounce it into rust-admin or rust-support, respectively. If you provide an argument of a rust-ticket id, they will append the message to an existing ticket.
 
@@ -156,13 +156,13 @@
 
   cat msg | rustmea 4242
 
-Adding people to a Rust CC list
+{subsection: Adding people to a Rust CC list}
 
 You can add users to the CC list using appenda and appends:
 
   appenda 9444 another.person@globus.example.com
 
-X-Rust header commands
+{subsection: X-Rust header commands}
 
 Also, when you're sending email to RUST, you can do certain actions with "X-Rust headers". These are special mail headers you can put in your message to tell RUST to do certain things. I have hacked RUST here so that these "mail headers" don't really have to be headers for the benefit of all the poor souls using Eudora or Microshaft's mail program that can't add their own email headers to their outgoing email. Now, not only does RUST scan through your email headers looking for an X-Rust: header, you can have such a line anywhere in your message body (so long as it's at the very beginning of a line). When your message goes to RUST, RUST would rip that line out of the message (so no one would even see it) and perform the request actions.
 
@@ -189,7 +189,8 @@
   X-Rust: set status pending, set eta March 15, assign stanis
 
 This would set the status to pending, the estimated time of arrival (action?) to March 15, and assign the ticket to Tom. That's probably way more complicated than most of you need to do... mostly you just need a way to resolve (and maybe re-assign tickets to someone else).
-More help
+
+{subsection: More help}
 
 For more info:
 
@@ -197,11 +198,13 @@
   action --help
 
 Also, system documentation is at /p/condor/home/rust/docs/HOWTO.
-Searching RUST
+
+{subsection: Searching RUST}
 
 To ease searching of RUST Alain Roy added a protoype glimpse search. Because of the size of the index (150mB as of June 20, 2003), it's on the local disk of chopin. You'll need to log into chopin to do searches. Use /scratch/roy/rustglimpse/search-rust to return the names of files that include your search term. use /scratch/roy/rustglimpse/search-rust-long to return the actual lines that match (ala grep).
 
 (Unfinished as of June 4 when Alain released his prototype: 1. Move the index into AFS? It's big and AFS might by slow. 2. Regenerate the index nightly, probably through cron. The indexing takes an hour or so.)
+
 RUST etiquette
 1) When to respond: