diff --git a/isomorphism-class.cabal b/isomorphism-class.cabal
--- a/isomorphism-class.cabal
+++ b/isomorphism-class.cabal
@@ -1,7 +1,7 @@
 cabal-version: 3.0
 
 name: isomorphism-class
-version: 0.1.0.7
+version: 0.1.0.8
 synopsis: Isomorphism typeclass solving the conversion problem
 homepage: https://github.com/nikita-volkov/isomorphism-class
 bug-reports: https://github.com/nikita-volkov/isomorphism-class/issues
diff --git a/library/IsomorphismClass.hs b/library/IsomorphismClass.hs
--- a/library/IsomorphismClass.hs
+++ b/library/IsomorphismClass.hs
@@ -5,9 +5,9 @@
 --
 -- Have you ever looked for a @toString@ function? How often do you
 -- import @Data.Text.Lazy@ only to call its 'Data.Text.Lazy.fromStrict'? How
--- about importing @Data.Text@ only to to call its 'Data.Text.unpack'? How
+-- about importing @Data.Text@ only to call its 'Data.Text.unpack'? How
 -- about going thru the always fun sequence of
--- importing @Data.ByteString.Builder@ only to to call its
+-- importing @Data.ByteString.Builder@ only to call its
 -- 'Data.ByteString.Builder.toLazyByteString' and then importing
 -- @Data.ByteString.Lazy@ only to call its 'Data.ByteString.Lazy.toStrict'?
 --
@@ -92,8 +92,8 @@
     -- = Why no instance for Text/ByteString?
     --
     -- It is not a total isomorphism. Yes, you can represent every Text value using ByteString.
-    -- However, not every ByteString can be decoded as valid Text. It doesn't matter which encoding you apply whatever encoding you apply.
-    -- So it doesn't matter whether it's UTF8 or ISO-8859, or any other.
+    -- However, not every ByteString can be decoded as valid Text.
+    -- It doesn't matter which encoding you apply: UTF8, ISO-8859 or any other.
     --
     -- = String/Text is not exactly a valid isomorphism
     --