[Rt-commit] rt branch, 4.0/documentation-reorg, updated. rt-4.0.0rc6-85-ge688bc2

[Kevin Falcone]

The branch, 4.0/documentation-reorg has been updated
       via  e688bc2bbf9ee481eb49ec2603472010bba9aa95 (commit)
       via  11eecad68e7254560db8f612f2e562656d5e7ce1 (commit)
       via  a2b14ce9cabbee0b6798ef69a18839702bbe9b0e (commit)
      from  6df9efcb18c90f27500154811bc9c515c92ed99f (commit)

Summary of changes:
 docs/customizing/articles_introduction.pod |    4 ++--
 docs/customizing/queue_subject_tag.pod     |    4 ++--
 docs/extending/external_custom_fields.pod  |    4 ++--
 3 files changed, 6 insertions(+), 6 deletions(-)

- Log -----------------------------------------------------------------
commit a2b14ce9cabbee0b6798ef69a18839702bbe9b0e
Author: Kevin Falcone <falcone at bestpractical.com>
Date:   Thu Mar 17 14:23:21 2011 -0400

    point out that articles aren't only for mail replies

diff --git a/docs/customizing/articles_introduction.pod b/docs/customizing/articles_introduction.pod
index 7a496e1..ea49b05 100644
--- a/docs/customizing/articles_introduction.pod
+++ b/docs/customizing/articles_introduction.pod
@@ -3,8 +3,8 @@
 
 Articles are a way of managing stock answers or frequently asked
 questions.  Articles are a collection of custom fields whose values can
-be easily inserted into ticket replies.  They are organized into classes
-and topics.
+be easily inserted into ticket replies or searched and browsed within
+RT.  They are organized into classes and topics.
 
 =head2 UI
 

commit 11eecad68e7254560db8f612f2e562656d5e7ce1
Author: Kevin Falcone <falcone at bestpractical.com>
Date:   Thu Mar 17 14:30:00 2011 -0400

    more englishification

diff --git a/docs/customizing/queue_subject_tag.pod b/docs/customizing/queue_subject_tag.pod
index b2c4ff1..1b4112d 100644
--- a/docs/customizing/queue_subject_tag.pod
+++ b/docs/customizing/queue_subject_tag.pod
@@ -19,9 +19,9 @@ Usually, you won't need to add any code to your templates to make the
 subject tags work. A tag will automatically be added in the beginning of
 subject before sending email out.
 
-If you want to subjects to be "prefix [tag] real subject" like in
+If you want your subject to be "prefix [tag] real subject" like in
 default Autoreply template, you can use the following code in templates
-to place of the subject tag:
+to control the placement of the subject tag:
 
     { $Ticket->SubjectTag }
 

commit e688bc2bbf9ee481eb49ec2603472010bba9aa95
Author: Kevin Falcone <falcone at bestpractical.com>
Date:   Thu Mar 17 14:33:10 2011 -0400

    spellcheck

diff --git a/docs/extending/external_custom_fields.pod b/docs/extending/external_custom_fields.pod
index 1b3bb50..c6730ae 100644
--- a/docs/extending/external_custom_fields.pod
+++ b/docs/extending/external_custom_fields.pod
@@ -10,7 +10,7 @@ data from the external source.
 =head2 Introduction into writing source of values
 
 For each type of data source that you want, you'll need to put a file in
-F</opt/rt4/local/lib/RT/CustomFieldValues/> (or equivilent if you
+F</opt/rt4/local/lib/RT/CustomFieldValues/> (or equivalent if you
 installed RT into someplace other than F</opt/rt4>). To get a sense of
 the code that you'll need to write, take a look at the code in
 L</opt/rt4/lib/RT/CustomFieldValues/Groups.pm> for a simple example
@@ -49,7 +49,7 @@ There are two main methods you want to override:
 =item SourceDescription
 
 This method should return a string describing the data source; this is
-the identifier which the adimistrator will see in the dropdown in the
+the identifier which the administrator will see in the dropdown in the
 web interface. See L</Configuration>.
 
 =item ExternalValues

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