Fixes typos

And improves docs of aspell.t trying to deal with #975

doc/Language/hashmap.pod6

@@ -19,7 +19,7 @@ the two methods above, as well as the default Hash behavior.
     say (%).^name ;# OUTPUT: «Hash␤»
 
 Inversely, you cannot use the C<%> sigil if the C<Associative> role is not mixed
-in, but since this role does not have any associater properties, you will have
+in, but since this role does not have any associated properties, you will have
 to redefine the behavior of the L<hash subscript
 operator|/language/operators#postcircumfix_{_}>. In order to do that, there
 are several functions you will have to override:
@@ -65,7 +65,7 @@ say %logger<2018-04-22>:exists;  # OUTPUT: «False»
 
 =end code
 
-In this case, we are definning a logger with Associative semantics that would be
+In this case, we are defining a logger with Associative semantics that would be
 able to use dates (or a part of them) as keys. Since we are parametrizing
 C<Associative> to those particular classes, C<of> will return the value type we
 have used, C<Cool> in this case (we can log lists or strings only). Mixing the C<Associative> role gives it the right to use the C<%> sigil; binding is needed in the definition since C<%>-sigilled variables get by default the C<Hash> type.
@@ -96,7 +96,7 @@ immutable. Once a key has been paired with a value, this pairing cannot be
 changed.
 
 Maps and hashes are usually stored in variables with the percent C<%> sigil,
-which is ussed to indicate they are Associative.
+which is used to indicate they are Associative.
 
 Hash and map elements are accessed by key via the C<{ }> postcircumfix operator:
 

xt/aspell.t

@@ -7,15 +7,15 @@ use Test-Files;
 
 =begin overview
 
-Spell check all the pod files in the documentation directory.
+Spell check all the pod and most markdown files in the documentation directory.
 
 Ignore case, and provide a repo-specific list of approved words,
 which include technical jargon, method and class names, etc.
 
 If the test fails, you can make it pass again by changing the
 text (fixing the spelling issue), or adding the new word to
-xt/words.pws (if it's a word, a class/method name, known
-program name, etc.), or to xt/code.pws (if it's a fragment of
+C<xt/words.pws> (if it's a word, a class/method name, known
+program name, etc.), or to C<xt/code.pws> (if it's a fragment of
 text that is part of a code example)
 
 =end overview

xt/words.pws

@@ -1419,3 +1419,5 @@ Mattijsen
 TKey
 DateHash
 evir
+parametrizing
+Cro