[Rt-commit] rt branch, 4.4/assets-documentation-no-etc, created. rt-4.2.12-369-ge11dfd5

[Todd Wade]

The branch, 4.4/assets-documentation-no-etc has been created
        at  e11dfd5db9328525733dabdd570f413a1a37c1ea (commit)

- Log -----------------------------------------------------------------
commit e11dfd5db9328525733dabdd570f413a1a37c1ea
Author: Todd Wade <todd at bestpractical.com>
Date:   Fri Oct 30 14:59:46 2015 -0400

    make RT_Config.pm links consistent in assets documentation
    
    Use F<RT_Config.pm> instead of F<etc/RT_Config.pm> for consistency

diff --git a/docs/assets.pod b/docs/assets.pod
index b8ab169..3ef0ec2 100644
--- a/docs/assets.pod
+++ b/docs/assets.pod
@@ -156,7 +156,7 @@ Lifecycles configuration (see "Lifecycles" in F<RT_Config.pm>).  The default
 lifecycle is named "assets".  You're free to modify it as much as you'd like,
 or add your own lifecycles.  Each catalog may have its own lifecycle.
 
-For the default "assets" configuration, see F<etc/RT_Config.pm>.
+For the default "assets" configuration, see F<RT_Config.pm>.
 
 =head2 Field organization
 
@@ -170,7 +170,7 @@ By default your CFs will appear in a B<Custom Fields> box on the asset display
 page and will be editable from a box of the same name on the B<Basics> editing
 page.
 
-Using the C<%CustomFieldGroupings> option (documented in F<etc/RT_Config.pm>),
+Using the C<%CustomFieldGroupings> option (documented in F<RT_Config.pm>),
 you can move individual CFs by name into one of the four built-in groupings
 (B<Basics>, B<People>, B<Dates>, and B<Links>) or create your own just by
 naming it.  An example, assuming a date CF named "Purchased" and two "enter one

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