diff --git a/Cargo.lock b/Cargo.lock
index 98c0641..3ea9855 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -3,7 +3,7 @@ name = "secretshare"
 version = "0.1.2"
 dependencies = [
  "crc24 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
- "getopts 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
+ "getopts 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)",
  "rand 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
  "rustc-serialize 0.2.12 (registry+https://github.com/rust-lang/crates.io-index)",
 ]
@@ -15,7 +15,7 @@ source = "registry+https://github.com/rust-lang/crates.io-index"
 
 [[package]]
 name = "getopts"
-version = "0.2.1"
+version = "0.2.3"
 source = "registry+https://github.com/rust-lang/crates.io-index"
 dependencies = [
  "log 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
diff --git a/README.md b/README.md
index e4d6c69..8620fb1 100644
--- a/README.md
+++ b/README.md
@@ -84,10 +84,10 @@ Shamir's secret sharing is known to have the perfect secrecy property.
 In the context of (K,N)-threshold schemes this means that if you have
 less than K shares available, you have absolutely no information about
 what the secret is. None. The checksums that are included in the shares
-also don't reveal anything about the secret. They are just a simple
-integrity protection of the shares themselves. In other words, given
-a share without checksum, we can derive a share with a checksum. This
-obviously does not add any new information.
+also don't reveal anything about the secret except for its length.
+They are just a simple integrity protection of the shares themselves.
+In other words, given a share without checksum, we can derive a share
+with a checksum. This obviously does not add any new information.
 
 # Galois field