You've come a long way, baby!
Egads! White space. Lots of it! strict, warnings, polite use of Exporter (with @EXPORT_OK), consistent use of indenting, documentation. All good!
Count Zero has made great suggestions. Here's one more. There are some standard conventions about how sections of POD are organized. Here's how I would revise your pod to use more standard headings and organization. However, there are many styles out there and I encourage you to check CPAN for further examples, as well.
Games::Random::Alignment - generates random alignments for AD&D 2nd Ed
use Games::Random::Alignmnet qw(random_alignment);
# generate lawful, chaotic, good, evil or neutral
# generate good, neutral or evil
# generate lawful, neutral, or chaotic
# generate lawful evil, neutral evil, or chaotic evil.
# generate lawful good, neutral good, or chaotic good.
# generate chaotic good, chaotic neutral, or chaotic evil.
# generate lawful good, lawful neutral, or lawful evil.
# generate lawful neutral, true neutral, or chaotic neutral.
# generate neutral good, true neutral, or neutral evil.
# generate any two part alignment.
This module generates random alignments for AD&D 2nd Edition. When yo
+u want to generate a random alignment with this module, you can choos
+e from any of the alignment axes. For examples, see the L</USAGE> se
Lady Aleena with lots of help from DrForr, whoppix, and rindolf in the
+ #perlcafe on freenode.
As you have already probably figured out indenting pod
causes it to be formatted as code, so all of the usage section will look like code samples. L</Some heading name here> lets you create a link to any other heading (a name introduced by =head1, =head2, etc) in your pod. See perlpod for all the gory details.