fixup! document GHC-55666

Author: HugoPeters1024

message-index/messages/GHC-55666/example/after/Bang_on_unlifted_type.hs

@@ -1,3 +1,5 @@
+{-# LANGUAGE MagicHash #-}
+
 module Bang_on_unlifted_type where
 
 import GHC.Base (Int#)

message-index/messages/GHC-55666/example/before/Bang_on_unlifted_type.hs

@@ -1,3 +1,5 @@
+{-# LANGUAGE MagicHash #-}
+
 module Bang_on_unlifted_type where
 
 import GHC.Base (Int#)

message-index/messages/GHC-55666/example/index.md

@@ -1,3 +1,13 @@
 ---
 title: Bang (!) on unlifted type
 ---
+
+```
+src/MyLib.hs:16:5: warning: [GHC-55666] [-Wredundant-strictness-flags]
+    * Strictness flag has no effect on unlifted type `Int#'
+    * In the definition of data constructor `MkT'
+      In the data type declaration for `T'
+   |
+   |   = MkT !Int#
+   |     ^^^^^^^
+```

message-index/messages/GHC-55666/index.md

@@ -7,11 +7,11 @@ introduced: GHC 9.6.1
 ---
 
 A strictness annotation (also called a bang: `!`) can be used to denote that a value should not be evaluated lazily.
-In some cases this can lead to faster code because fewer heap allocation are required.
+In some cases this can lead to faster code because fewer heap allocations are required.
 Here it is used to mark a that a field in a datatype should not be evaluated lazily.
 
 However, unlifted types like `Int#` are strict by definition because they are a value,
 not a pointer to a potentially unevaluated value (thunk).
 
-Therefore, adding strictness annotations to unlifted types or fields of such types are redundant.
+Therefore, adding strictness annotations to unlifted types or fields of such types is redundant.
 They should be omitted to avoid confusion.