From a9abc328deb17e65aebc0a3e6333a1095ed55841 Mon Sep 17 00:00:00 2001
From: "Will \"Coke\" Coleda" <will@coleda.com>
Date: Wed, 12 Oct 2016 11:33:05 -0400
Subject: [PATCH] fix typos

---
 doc/Language/tables.pod6                          | 2 +-
 doc/Language/typesystem.pod6                      | 2 +-
 doc/Type/Signature.pod6                           | 2 +-
 doc/Type/X/Parameter/MultipleTypeConstraints.pod6 | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/Language/tables.pod6 b/doc/Language/tables.pod6
index f21f8726d..4385c0e9b 100644
--- a/doc/Language/tables.pod6
+++ b/doc/Language/tables.pod6
@@ -262,7 +262,7 @@ r0c0    r0c1
 
 Notice the second row has the two words separated by a visible
 character (V<'|'>) but the character is not recognized as a column
-separator because it doen't have an adjacent WS character on both
+separator because it doesn't have an adjacent WS character on both
 sides of it.  B<This is an invalid table because the first row has two
 columns while the second row has only one column, and it will trigger
 an exception.>.
diff --git a/doc/Language/typesystem.pod6 b/doc/Language/typesystem.pod6
index 30660b8cc..5549a3dae 100644
--- a/doc/Language/typesystem.pod6
+++ b/doc/Language/typesystem.pod6
@@ -358,7 +358,7 @@ C<trusts>. A forward declaration of the trusted class may be required.
 
 =head3 Versioning and Authorship
 
-Versioning and authership can be applied via adverbs X«C«:ver<>»|:ver<> (class)» and X«C«:auth<>»|:auth<> (class)».
+Versioning and authorship can be applied via adverbs X«C«:ver<>»|:ver<> (class)» and X«C«:auth<>»|:auth<> (class)».
 Both take a string as argument, for C<:ver> the string is converted to a
 L<Version|/type/Version> object. To query a class version and author use
 C<.^ver> and C<^.auth>.
diff --git a/doc/Type/Signature.pod6 b/doc/Type/Signature.pod6
index 8b2c52095..40e3b3256 100644
--- a/doc/Type/Signature.pod6
+++ b/doc/Type/Signature.pod6
@@ -155,7 +155,7 @@ the C<where>-clause inside the sub-signature.
 L<Optional arguments|#Optional_and_Mandatory_Parameters> can have constraints,
 too. Any C<where> clause on any parameter will be executed, even if it's
 optional and not provided by the caller. In that case you may have to guard
-against undefined values whitin the C<where> clause.
+against undefined values within the C<where> clause.
 
     sub f(Int $a, UInt $i? where { !$i.defined or $i > 5 } ) { ... }
 
diff --git a/doc/Type/X/Parameter/MultipleTypeConstraints.pod6 b/doc/Type/X/Parameter/MultipleTypeConstraints.pod6
index b22972acb..35e7f3d03 100644
--- a/doc/Type/X/Parameter/MultipleTypeConstraints.pod6
+++ b/doc/Type/X/Parameter/MultipleTypeConstraints.pod6
@@ -17,7 +17,7 @@ sub f(Cool Real $x) { }
 produces
 
 =for code :skip-test
-Parameter $x may onle have one prefix type constraint
+Parameter $x may only have one prefix type constraint
 
 =head1 Methods