[Rt-commit] rt branch, automating-rt-docs, updated. rt-4.2.14-9-gdb707e6

[Craig Kaiser]

The branch, automating-rt-docs has been updated
       via  db707e681452e17835f31e580501545603e3a27a (commit)
      from  c229a9233284345294abb4a96b39c843365bf3be (commit)

Summary of changes:
 docs/automating_rt.pod | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

- Log -----------------------------------------------------------------
commit db707e681452e17835f31e580501545603e3a27a
Author: craig <craig at bestpractical.com>
Date:   Mon Oct 16 10:39:26 2017 -0400

    Adding documentatiion for automating-rt, using rt-crontool with multiple --action parameters.

diff --git a/docs/automating_rt.pod b/docs/automating_rt.pod
index b1a7e2d..fdf997a 100644
--- a/docs/automating_rt.pod
+++ b/docs/automating_rt.pod
@@ -78,7 +78,7 @@ The C<--action> argument is set to L<RT::Action> which is the base class
 for RT actions. Since this class doesn't perform any action itself, this
 command will just output the results of the TicketSQL search.
 
-=head2 Multiple --Action parameters
+=head2 Multiple --Action Parameters
 
     /opt/rt4/bin/rt-crontool \
       --search RT::Search::FromSQL \
@@ -91,7 +91,9 @@ command will just output the results of the TicketSQL search.
 
 rt-crontool can also take more than one --action parameter to perform multiple steps are a time. In the example above
 two actions are completed first it checks for any tickets with a "stalled" status and then marks them as resolved.
-As well as notifies the Requestors on the ticket of the change.p
+As well as notifies the Requestors on the ticket of the change.
+
+
 =head1 Auto-resolve Aged Tickets
 
 You can auto-set status based on any criteria you can define in

-----------------------------------------------------------------------