@@ -19,9 +19,9 @@
19-- A Haskell numeric type is considered to be compatible with all
19-- A Haskell numeric type is considered to be compatible with all
20-- PostgreSQL numeric types that are less accurate than it. For instance,
20-- PostgreSQL numeric types that are less accurate than it. For instance,
21-- the Haskell 'Double' type is compatible with the PostgreSQL's 32-bit
21-- the Haskell 'Double' type is compatible with the PostgreSQL's 32-bit
22−-- @Int@ type because it can represent a @Int@ exactly. On the other hand,
22+-- @int@ type because it can represent a @int@ exactly. On the other hand,
23−-- since a 'Double' might lose precision if representing a 64-bit @BigInt@,
23+-- since a 'Double' might lose precision if representing PostgreSQL's 64-bit
24−-- the two are /not/ considered compatible.
24+-- @bigint@, the two are /not/ considered compatible.
26-- Because 'FromField' is a typeclass, one may provide conversions to
26-- Because 'FromField' is a typeclass, one may provide conversions to
27-- additional Haskell types without modifying postgresql-simple. This is
27-- additional Haskell types without modifying postgresql-simple. This is