Fix some typos in the docs for the allomorph types

Raku · May 25, 2016 · 42a5c98 · 42a5c98
1 parent fcfeaf7
commit 42a5c98
Show file tree

Hide file tree

Showing 4 changed files with 8 additions and 8 deletions.
diff --git a/doc/Type/ComplexStr.pod b/doc/Type/ComplexStr.pod
@@ -6,7 +6,7 @@
 
     class ComplexStr is Complex is Str 
 
-The dual value types (often referred to as L<allomorphs|/language/glossary#Allomorph>
+The dual value types (often referred to as L<allomorphs|/language/glossary#Allomorph>)
 allow for the representation of a value as both a string and a numeric type, typically
 they will be created for you when the context is "stringy" but they can be determined
 to be numbers, such as in some L<quoting constructs|/language/quoting>:
@@ -37,7 +37,7 @@ directly the values can be whatever is required:
 
     method Numeric
 
-The numeric coercion that is applied when the C<ComplexStr> is used in a numeric context,
+The numeric coercion is applied when the C<ComplexStr> is used in a numeric context,
 such as a numeric comparison or smart match against a numeric value. It will return
 the C<Complex> value.
 

diff --git a/doc/Type/IntStr.pod b/doc/Type/IntStr.pod
@@ -6,7 +6,7 @@
 
     class IntStr is Int is Str 
 
-The dual value types (often referred to as L<allomorphs|/language/glossary#Allomorph>
+The dual value types (often referred to as L<allomorphs|/language/glossary#Allomorph>)
 allow for the representation of a value as both a string and a numeric type, typically
 they will be created for you when the context is "stringy" but they can be determined
 to be numbers, such as in some L<quoting constructs|/language/quoting>:
@@ -37,7 +37,7 @@ directly the values can be whatever is required:
 
     method Numeric
 
-The numeric coercion that is applied when the C<IntStr> is used in a numeric context,
+The numeric coercion is applied when the C<IntStr> is used in a numeric context,
 such as a numeric comparison or smart match against a numeric value. It will return
 the C<Int> value.
 

diff --git a/doc/Type/NumStr.pod b/doc/Type/NumStr.pod
@@ -6,7 +6,7 @@
 
     class NumStr is Num is Str 
 
-The dual value types (often referred to as L<allomorphs|/language/glossary#Allomorph>
+The dual value types (often referred to as L<allomorphs|/language/glossary#Allomorph>)
 allow for the representation of a value as both a string and a numeric type, typically
 they will be created for you when the context is "stringy" but they can be determined
 to be numbers, such as in some L<quoting constructs|/language/quoting>:
@@ -37,7 +37,7 @@ directly the values can be whatever is required:
 
     method Numeric
 
-The numeric coercion that is applied when the C<NumStr> is used in a numeric context,
+The numeric coercion is applied when the C<NumStr> is used in a numeric context,
 such as a numeric comparison or smart match against a numeric value. It will return
 the C<Num> value.
 

diff --git a/doc/Type/RatStr.pod b/doc/Type/RatStr.pod
@@ -6,7 +6,7 @@
 
     class RatStr is Rat is Str 
 
-The dual value types (often referred to as L<allomorphs|/language/glossary#Allomorph>
+The dual value types (often referred to as L<allomorphs|/language/glossary#Allomorph>)
 allow for the representation of a value as both a string and a numeric type, typically
 they will be created for you when the context is "stringy" but they can be determined
 to be numbers, such as in some L<quoting constructs|/language/quoting>:
@@ -37,7 +37,7 @@ directly the values can be whatever is required:
 
     method Numeric
 
-The numeric coercion that is applied when the C<RatStr> is used in a numeric context,
+The numeric coercion is applied when the C<RatStr> is used in a numeric context,
 such as a numeric comparison or smart match against a numeric value. It will return
 the C<Rat> value.