Fix typos not found by codespell

INSTALL.rst

@@ -267,7 +267,7 @@ features to enable or disable. You can also get a description of these
 options by typing ``./configure --help``.
 
 Fine tuning of the installation directories (the default value for each option
-is displayed within brakets):
+is displayed within brackets):
 
 .. instopt:: --bindir=DIR
 

contrib/modulefiles/scheme/racket/5.0.2

@@ -3,7 +3,7 @@
 ##      GNU Module
 ##
 proc ModulesHelp { } {
-  puts stderr "\tRacket (forermly Dr Scheme) is an interactive, integrated,\n"
+  puts stderr "\tRacket (formerly Dr Scheme) is an interactive, integrated,\n"
   puts stderr "\tgraphical programming environment for Scheme.\n"
   puts stderr "\tIt is available on all machines in CS and IT. To use it,\n"
   puts stderr "\tload this module and type: drracket\n"

doc/source/cookbook/new-features-without-breaking-old-module.rst

@@ -111,4 +111,4 @@ current user::
 .. note::
 
    As the new Tcl variables are introduced in Modules 4.7, the use of the new
-   ``uergroups`` sub-command will only be triggered starting Modules 4.7.
+   ``usergroups`` sub-command will only be triggered starting Modules 4.7.

doc/source/design/extended-default.rst

@@ -42,7 +42,7 @@ Specification
 
 - If :mconfig:`implicit_default` is disabled
 
-    - it makes ``extended_default`` inoperant if queried version does not include a defined default
+    - it makes ``extended_default`` inoperative if queried version does not include a defined default
     - even if only one modulefile matches query
     - with situation described above query soft/1 returns soft/1.1
     - but query soft/2 returns an error as no default is found among version 2 modulefiles

doc/source/design/hide-or-forbid-modulefile.rst

@@ -80,7 +80,7 @@ Specification
 
     - Visibility is however enabled if hidden module is specifically searched
 
-        - On all context hidden module *mod/1.0* is included in result for instance if *mod/1.0* or *mod@1.0,2.0* are specficied
+        - On all context hidden module *mod/1.0* is included in result for instance if *mod/1.0* or *mod@1.0,2.0* are specified
         - But hidden module *mod/1.0* is excluded from result if *mod@:2.0* or *mod@1:* are specified
         - And is also excluded from result if *mod* or *mod/** are specified when *mod/1.0* is set default
         - Unless if search is made to select one module since in this context a *mod* search query is equivalent to *mod/default*

doc/source/design/insensitive-case.rst

@@ -42,8 +42,8 @@ Specification
     - like *soft*, *soFT*, *SoFt*, *SOFT* filenames
     - query *SOFT* returns *SOFT* (exact match is returned among possibilities)
     - query *SoFt* returns *SoFt* (exact match is returned among possibilities)
-    - query *SOft* returns *soft* (highest dictionarily-sorted match is returned among possibilities)
-    - query *soFt* returns *soft* (highest dictionarily-sorted match is returned among possibilities)
+    - query *SOft* returns *soft* (highest lexicographically sorted match is returned among possibilities)
+    - query *soFt* returns *soft* (highest lexicographically sorted match is returned among possibilities)
 
 - When icase is enabled for search context it applies to
 

doc/source/design/sticky-modules.rst

@@ -26,7 +26,7 @@ Specification
     - as modulefile targeted by symbol or alias does not inherit their tags
     - so a sticky or super-sticky tag set on a symbolic version or alias has no effect
 
-- Sticky module can be swapped with another version from same module when stickness is defined over module parent name
+- Sticky module can be swapped with another version from same module when stickiness is defined over module parent name
 
     - For instance if stickyness is defined over module *foo*, *foo/1.0* can be swapped with *foo/2.0*
     - Such swap could occur from a ``restore`` or a ``switch`` sub-command
@@ -37,7 +37,7 @@ Specification
         - it means stickyness applies to the module versions
         - thus they cannot be swapped by another version
 
-    - In case stickness is defined over module parent name and another ``module-tag`` defines stickyness over specific module version name
+    - In case stickiness is defined over module parent name and another ``module-tag`` defines stickyness over specific module version name
 
         - it means stickyness applies to the module version
         - thus these versions targeted specifically with ``module-tag`` cannot be swapped by another version from same module