Typos in user manual and code: recurisve -> recursive

compiler/typecheck/TcInstDcls.hs

@@ -142,7 +142,7 @@ Note [Instances and loop breakers]
 
 * Instead the idea is to inline df_i into op1_i, which may then select
   methods from the MkC record, and thereby break the recursion with
-  df_i, leaving a *self*-recurisve op1_i.  (If op1_i doesn't call op at
+  df_i, leaving a *self*-recursive op1_i.  (If op1_i doesn't call op at
   the same type, it won't mention df_i, so there won't be recursion in
   the first place.)
 

compiler/typecheck/TcSimplify.hs

@@ -480,7 +480,7 @@ signature
 where F is a type function.  This happened in Trac #3972.
 
 We could do more than once but we'd have to have /some/ limit: in the
-the recurisve case, we would go on forever in the common case where
+the recursive case, we would go on forever in the common case where
 the constraints /are/ satisfiable (Trac #10592 comment:12!).
 
 For stratightforard situations without type functions the try_harder

docs/users_guide/glasgow_exts.rst

@@ -11376,7 +11376,7 @@ obfuscates matters, so we do not do so here.)
 
 The translation is carefully crafted to make bang patterns meaningful
 for reursive and polymorphic bindings as well as straightforward
-non-recurisve bindings.
+non-recursive bindings.
 
 Here are some examples of how this translation works. The first
 expression of each sequence is Haskell source; the subsequent ones are