Remove misleading "deep equality" claim.

Testing tuple equality with === gives results identical to testing the
*shallow* identities of the elements in the tuple. Equality checking does
not recurse further into the elements of the tuple (nor should it), so
"deep equality checking" could be misleading.

Deeply nested tuples containing other tuples can be deeply compared in
constant time using ===, of course, and this property would extend to
other internalized persistent data structures. Nevertheless, it's
important for users to realize that this library treats "normal" objects
and primitive values the same way a Map would treat them.

With that said, "constant-time equality testing (===)" is still an
accurate claim without the "deep" adjective.

Author: benjamn

README.md

@@ -1,3 +1,3 @@
 # immutable-tuple [![Build Status](https://travis-ci.org/benjamn/immutable-tuple.svg?branch=master)](https://travis-ci.org/benjamn/immutable-tuple)
 
-Immutable finite list objects with constant-time deep equality testing (`===`) and no memory leaks.
+Immutable finite list objects with constant-time equality testing (`===`) and no memory leaks.

package.json

@@ -1,7 +1,7 @@
 {
   "name": "immutable-tuple",
   "version": "0.4.1",
-  "description": "Immutable finite list objects with constant-time deep equality testing (===) and no memory leaks",
+  "description": "Immutable finite list objects with constant-time equality testing (===) and no memory leaks",
   "license": "MIT",
   "author": {
     "name": "Ben Newman",
@@ -35,6 +35,7 @@
     "interned",
     "internalized",
     "memoization",
+    "equality",
     "deep equality",
     "weakmap"
   ],