[Rt-commit] rt branch, 4.0/format-strings, updated. rt-4.0.23-24-gf7724bf

[Shawn Moore]

The branch, 4.0/format-strings has been updated
       via  f7724bf3a47cd5fe10dfcc31caa92ba4077018a9 (commit)
      from  574830a4690af7c5881282f9753442f85b572fa2 (commit)

Summary of changes:
 docs/format-strings.pod | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

- Log -----------------------------------------------------------------
commit f7724bf3a47cd5fe10dfcc31caa92ba4077018a9
Author: Shawn M Moore <shawn at bestpractical.com>
Date:   Wed Jun 3 14:07:21 2015 -0400

    Tiny improvements to format-strings doc

diff --git a/docs/format-strings.pod b/docs/format-strings.pod
index 1757a87..6040d74 100644
--- a/docs/format-strings.pod
+++ b/docs/format-strings.pod
@@ -63,7 +63,7 @@ C<%AdminSearchResultFormat>
 Format strings are comma-separated lists of single-quoted strings.
 Since they're quoted strings of quoted strings, to prevent having to
 escape all of the quotes, they often use the C<qq{ ... }> operator in
-perl, which is just a fancy set of double-quotes.  For instance:
+Perl, which is just a fancy set of double-quotes.  For instance:
 
     Set( $DefaultSearchResultFormat, "'__id__','__Status__');
 
@@ -71,6 +71,7 @@ perl, which is just a fancy set of double-quotes.  For instance:
 
     Set( $DefaultSearchResultFormat, qq{ '__id__','__Status__' } );
 
+...except that it becomes easier to use double-quote characters.
 
 =head2 Elements
 
@@ -127,7 +128,7 @@ the list will be formatted on two lines.  For example, the format:
 
     '__id__', '__Subject__', '__NEWLINE__', '__Status__', '__QueueName__'
 
-..will render a three-ticket set of results as:
+...will render a three-ticket set of results as:
 
 =for html
 <table class="example"><tr class="none"><th>#</th><th>Subject</th></tr><tr><th>Status</th><th>Queue</th></tr>

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