@@ -1,5 +1,8 @@
 Revision history for Perl extension Class::Accessor::Lite.
 
+0.06
+	- fix documentation issues (thanks to magnolia-k)
+
 0.05
 	- improve usage error checking: assert that the accessor lists passed through the "import" function are arrayrefs
 

@@ -19,4 +19,4 @@ no_index:
     - t
 resources:
   license: http://dev.perl.org/licenses/
-version: 0.05
+version: 0.06

@@ -30,11 +30,11 @@ THE USE STATEMENT
         passed through as an arrayref
 
     ro => \@name_of_the_properties
-        creates a write-only accessor for the name of the properties passed
+        creates a read-only accessor for the name of the properties passed
         through as an arrayref
 
-    rw => \@name_of_the_properties
-        creates a read-only accessor for the name of the properties passed
+    wo => \@name_of_the_properties
+        creates a write-only accessor for the name of the properties passed
         through as an arrayref
 
     For more detailed explanation read the following section describing the
@@ -70,11 +70,11 @@ FUNCTIONS
 FAQ
   Can I use "Class::Accessor::Lite" in an inherited module?
     Yes in most cases, when the class object in the super class is
-    implemeted using a hashref. However you _should_ _not_ create the
+    implemented using a hashref. However you _should_ _not_ create the
     constructor for the inherited class by calling
-    "Class::Accessor::Lite-"new()> or by "use Class::Accessor::Lite (new ="
-    1). The only other thing that "Class::Accessor::Lite" does is to set up
-    the accessor functions for given property names through a blessed
+    "<Class::Accessor::Lite-"new()>> or by "<use Class::Accessor::Lite (new
+    =" 1)>>. The only other thing that "Class::Accessor::Lite" does is to
+    set up the accessor functions for given property names through a blessed
     hashref.
 
   What happens when passing more than one arguments to the accessor?

@@ -2,7 +2,7 @@ package Class::Accessor::Lite;
 
 use strict;
 
-our $VERSION = '0.05';
+our $VERSION = '0.06';
 
 use Carp ();
 
@@ -172,11 +172,11 @@ creates a read / write accessor for the name of the properties passed through as
 
 =item ro => \@name_of_the_properties
 
-creates a write-only accessor for the name of the properties passed through as an arrayref
+creates a read-only accessor for the name of the properties passed through as an arrayref
 
-=item rw => \@name_of_the_properties
+=item wo => \@name_of_the_properties
 
-creates a read-only accessor for the name of the properties passed through as an arrayref
+creates a write-only accessor for the name of the properties passed through as an arrayref
 
 =back
 
@@ -210,7 +210,7 @@ DEPRECATED.  Use the new "use Class::Accessor::Lite (...)" style.
 
 =head2 Can I use C<Class::Accessor::Lite> in an inherited module?
 
-Yes in most cases, when the class object in the super class is implemeted using a hashref.  However you _should_ _not_ create the constructor for the inherited class by calling C<Class::Accessor::Lite->new()> or by C<use Class::Accessor::Lite (new => 1).  The only other thing that C<Class::Accessor::Lite> does is to set up the accessor functions for given property names through a blessed hashref.
+Yes in most cases, when the class object in the super class is implemented using a hashref.  However you _should_ _not_ create the constructor for the inherited class by calling C<<Class::Accessor::Lite->new()>> or by C<<use Class::Accessor::Lite (new => 1)>>.  The only other thing that C<Class::Accessor::Lite> does is to set up the accessor functions for given property names through a blessed hashref.
 
 =head2 What happens when passing more than one arguments to the accessor?