diff --git a/Concurrency.podspec b/Concurrency.podspec
index 2239e7e..0fd02b2 100644
--- a/Concurrency.podspec
+++ b/Concurrency.podspec
@@ -1,6 +1,6 @@
 Pod::Spec.new do |s|
   s.name             = 'Concurrency'
-  s.version          = '0.1.0'
+  s.version          = '1.0.0'
   s.summary          = 'A small toolkit for handling concurrency in Swift.'
 
   s.description      = <<-DESC
diff --git a/Concurrency/Info.plist b/Concurrency/Info.plist
index 16be3b6..8928fed 100644
--- a/Concurrency/Info.plist
+++ b/Concurrency/Info.plist
@@ -15,7 +15,7 @@
 	<key>CFBundlePackageType</key>
 	<string>APPL</string>
 	<key>CFBundleShortVersionString</key>
-	<string>1.0</string>
+	<string>1.0.0</string>
 	<key>CFBundleVersion</key>
 	<string>1</string>
 	<key>LSRequiresIPhoneOS</key>
diff --git a/README.md b/README.md
index e868a0c..f130770 100644
--- a/README.md
+++ b/README.md
@@ -209,6 +209,8 @@ goCallYourMother().then { (earful) in
 
 As you can see, much like the `onSuccess(_:)` and `onError(_:)` methods on [`Result`](#result), these return discardable references to the promise and can thus be chained and used together or independently of one another.
 
+__Side note:__ There's also a handy `finally(_:)` method as well, which will add a block to be executed after completion, regardless of success or failure. It executes after the given success or failure block.
+
 The real magic about Future is that `then(_:)` and `error(_:)` can be called as many times as needed, and each of the actions will execute in order. So, if you have a method which fetches a value and returns a promise, and there are multiple layers of the app that need to be updated with that value, you can pass that future along from method to method, tacking on success actions as you go.
 
 Yes, I know, an example is in order. So, let's say we have that same method from earlier: `func goCallYourMother() -> Future<AnEarful>`. We could propagate it along like so: