[Rt-commit] rt branch, 4.0/pod-spell, updated. rt-4.0.0rc6-154-g75fbf3e

[Shawn Moore]

The branch, 4.0/pod-spell has been updated
       via  75fbf3efe1e3c27ce4473a4bfaf47351f573e2c8 (commit)
      from  35929627949509ea2b1a721add4f30317e3d4582 (commit)

Summary of changes:
 lib/RT/ObjectCustomField.pm |   23 ++++++++++++-----------
 t/99-pod-spelling.t         |    1 +
 2 files changed, 13 insertions(+), 11 deletions(-)

- Log -----------------------------------------------------------------
commit 75fbf3efe1e3c27ce4473a4bfaf47351f573e2c8
Author: Shawn M Moore <sartak at bestpractical.com>
Date:   Thu Mar 17 19:21:17 2011 -0400

    Spellcheck lib/RT/ObjectCustomField.pm

diff --git a/lib/RT/ObjectCustomField.pm b/lib/RT/ObjectCustomField.pm
index 45286ed..5160f0c 100644
--- a/lib/RT/ObjectCustomField.pm
+++ b/lib/RT/ObjectCustomField.pm
@@ -144,20 +144,21 @@ sub CustomFieldObj {
 
 =head2 Sorting custom fields applications
 
-Custom fields sorted on multiple layers. First of all custom
-fields with different lookup type are sorted independently. All
-global custom fields have fixed order for all objects, but you
-can insert object specific custom fields between them. Object
-specific custom fields can be applied to several objects and
-be on different place. For example you have GCF1, GCF2, LCF1,
-LCF2 and LCF3 that applies to tickets. You can place GCF2
-above GCF1, but they will be in the same order in all queues.
-However, LCF1 and other local can be placed at any place
-for particular queue: above global, between them or below.
+Custom fields are sorted in multiple layers. First of all, custom fields with
+different lookup types are sorted independently. All global custom fields have
+fixed order for all objects, but you can insert object specific custom fields
+between them. Object-specific custom fields can be applied to several objects
+and be in different places.
+
+For example, you have C<GCF1>, C<GCF2>, C<LCF1>, C<LCF2> and C<LCF3> that each
+apply to tickets. You can place C<GCF2> above C<GCF1>, but they will be in the
+same order in all queues. However, C<LCF1> and other local custom fields can be
+placed at any place for particular queue: above globals, between them, or below
+globals.
 
 =head3 MoveUp
 
-Moves custom field up. See </Sorting custom fields applications>.
+Moves custom field up. See L</Sorting custom fields applications>.
 
 =cut
 
diff --git a/t/99-pod-spelling.t b/t/99-pod-spelling.t
index 709babf..88b8abe 100644
--- a/t/99-pod-spelling.t
+++ b/t/99-pod-spelling.t
@@ -121,3 +121,4 @@ subvalue
 subvalues
 formatter
 formatters
+lookup

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