diff --git a/lib/Data/Printer.pm b/lib/Data/Printer.pm
index 4d9f78e..bc0ef64 100644
--- a/lib/Data/Printer.pm
+++ b/lib/Data/Printer.pm
@@ -790,7 +790,7 @@ you want):
     p my @array = qw(a b c d);          # wrong
     my @array = qw(a b c d); p @array;  # right
 
-If you pass a nonexistant key/index to DDP using prototypes, they
+If you pass a nonexistent key/index to DDP using prototypes, they
 will trigger autovivification:
 
     use DDP;
diff --git a/lib/Data/Printer/Filter/Web.pm b/lib/Data/Printer/Filter/Web.pm
index ed62d41..37cec54 100644
--- a/lib/Data/Printer/Filter/Web.pm
+++ b/lib/Data/Printer/Filter/Web.pm
@@ -264,7 +264,7 @@ You may also customize the look and feel with the following options (defaults sh
 =head1 DESCRIPTION
 
 This is a filter plugin for L<Data::Printer>. It filters through several
-web-related objects and display their content in a (hopefully!) more userful
+web-related objects and display their content in a (hopefully!) more useful
 way than a regular dump.
 
 =head1 PARSED MODULES
diff --git a/lib/Data/Printer/Object.pm b/lib/Data/Printer/Object.pm
index 4b04be6..1da01fe 100644
--- a/lib/Data/Printer/Object.pm
+++ b/lib/Data/Printer/Object.pm
@@ -859,7 +859,7 @@ values, and when set to "off" it will never show the second value. (default: lax
 
 =head3 show_lvalue
 
-Let's you know whenever a value is an lvalue (default: 1)
+Lets you know whenever a value is an lvalue (default: 1)
 
 =head3 string_max
 
@@ -896,7 +896,7 @@ whether to use the character's names when escaping unicode (e.g. SNOWMAN instead
 
 =head3 print_escapes
 
-Wether to print invisible characters in strings, like \b, \n and \t (default: 0)
+Whether to print invisible characters in strings, like \b, \n and \t (default: 0)
 
 =head3 resolve_scalar_refs
 
diff --git a/lib/Data/Printer/Profile.pm b/lib/Data/Printer/Profile.pm
index 4eca0d4..3108de4 100644
--- a/lib/Data/Printer/Profile.pm
+++ b/lib/Data/Printer/Profile.pm
@@ -79,7 +79,7 @@ and the final outcome will be as if your setup said:
 However, that is of course only true when the profile is loaded together with
 the other settings. If you set a profile later, for instance as an argument to
 C<p()> or C<np()>, then the profile will override any previous settings -
-though it will still be overriden by other inline arguments.
+though it will still be overridden by other inline arguments.
 
 
 =head1 SEE ALSO